Jump to content

snave

Verified Members
  • Content Count

    57
  • Joined

  • Last visited

Community Reputation

11 Good

About snave

  • Rank
    Advanced Member
  • Birthday October 19

Profile Information

  • Gender
    Male
  • Location
    South Coast, UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Cloud morphing DOES NOT happen with AS installed. Only with SF Clouds chosen. You've added an additional engine that is affecting results, I suspect... and please stop assuming others were dumb enough to install AS into P3D. ASP4 is the product for P3Dv4.5. I have everything working with a clean installation of EF on top of a virgin installation of SF. No errors in the morphing department; no rushed formation of cloud layers, no snap-of-the-finger changes to weather.
  2. Five hours is indicative of only two things: 1: You don't have a clue how long it really took or 2: You don't have a clue what you needed to do. Which is it? Exaggeration for emphasis or clueless-ness..?
  3. While you're hotfixing, do you think it would be possible to just add Environment Force to proper integration with Sky Force? Unlike some, I don't care for `Active` anything, nor merging with any other addon and just want EF to be properly integrated with SF, as I thought was the intention? i.e. start SF - EF automatically loads, or vice versa... It is already noticeable how many times I forgot to start one or the other, and really I think EF should merge seamlessly with SF with a single launch, with only the lesser human beings with `other` poorer weather engines forced to launch first one, then the other... 😉
  4. As v4.4 changed the water settings in-sim, the answer to your question is `no`...
  5. I woud check that you have the correct permissions and try different combinations. REX 4 Texture Direct provides literally tens of thousands of combinations, but ALL selections are under the control of the user, unless you wish to try pre-prepared combinations made by other users. You can check the GUI to see what textures can be changed, but I would suggest ensuring your system is capable of making those changes - you need to be running the sim as administrator under Win 10. REX likewise.
  6. You need to define HOW you did the update: After installing Client and Content, you need to: 1: Re-run the REX installer for your chosen theme 2: Delete the temporary shader cache (NOT the ShadersHLSL folder) Did you do BOTH of these?
  7. So here's the funny thing - observation not support request although it may need patching!: Win7 64, P3D v3.2.3; REX Essentials + Overdrive used for weather engine; REX 4TD + SC (patched to SP6) used for textures I've noticed since installing the P3D v3.2.3 update as a series of install upgrades (Client, then Content, then Scenery) that it doesn't matter what I select in REX4 for Sun as the installed texture, it never changed. Now, I should qualify that by saying that I've really only noticed it since the arrival of Spring in the sim, when the small size of the sun prompted me to actually change the texture... It transpires that suneffect .cfg held in the %ProgramData%\Lockheed Martin\Prepar3d V3 had not been overwritten since 04/10/2015 - so clearly any overwrite instruction by REX is not being handled. Now, I didn't do a full install to update - I followed the L-M recommendations for updating in sequence - unlike the `clean` install this does NOT specify removal of the created folders: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3 (or the modified install location) %PROGRAMDATA%\Lockheed Martin\Prepar3D v3 %LOCALAPPDATA%\Lockheed Martin\Prepar3D v3 %APPDATA%\Lockheed Martin\Prepar3D v3 %USERPROFILE%\Documents\Prepar3D v3 Files The conclusion I draw - for contemplation and discussion by the developers - is that the new folder prioritisation implemented in V3 is somehow preventing the REX selected changes, even though they are indicated as `installed` in the REX GUI. Perhaps this is something that needs looking into? For anybody else who does find a similar issue this can be resolved by simply deleting suneffect.cfg from %ProgramData%\Lockheed Martin\Prepar3d V3 and restarting the sim and after making any changes in the REX GUI. It will pick up on the `new` suneffect.cfg and install the desired textures - but then writing that suneffect.cfg to the folder so, of course, next time textures are changed, the same procedure needs to be followed. I suspect this may not be the only file that is affected this way.
  8. So it's related solely to `Low Level` clouds? That's all I needed to know. Consider this resolved. Thanks.
  9. Thank you. Look forward to the review.
  10. Be careful with this advice. I have all too often seen people delete the ShadersHLSL folder, NOT the folder found in: C:\Users\YOUR NAME\AppData\Local\Lockheed Martin\Prepar3D v3\Shaders Robson, that is the folder to delete - it contains a large number of small files with a common naming convention like: v323_sm110_Shadow.fx_GS_01a5000026040001_0030332500000001.cso Alternatively, it seems that just opening REX 4 Texture Direct and making a selection for new textures then saving them now automatically deletes the temporary shader folder for you. So just make a selection after installing the latest Hotfix and you should be up and running.
  11. Re Update Service Pack 6 - Hotfix 1 - (build: 4.8.2016.0314) Please remove the auto shader deletion and turn it into an OPTIONAL feature. It's beyond annoying to change a minor texture set, only to have the whole sim have to rebuild all shaders. Also, have it delete the contents of the shader folder, not the folder itself. How can YOU know that there aren't modified shaders already present in that temp folder, unrelated to your sky, cloud, water textures? Can you specify which sections actually REQUIRE a shader rebuild? Seems what you have done here is blunt force trauma on what should have been a scalpel operation.
×
×
  • Create New...