Jump to content

RRVyper

Verified Members
  • Content Count

    49
  • Joined

  • Last visited

Everything posted by RRVyper

  1. I use Auto mode, too. After shutting down P3D (and waiting for the process to end ~ 15 sec.), open EF from the icon in the system tray, switch to manual mode and close EF. The next time you run EF, it will ask if you like to tweak, just say no. ๐Ÿ˜‰
  2. It's fixed in the next release, currently in alpha testing. However, it doesn't prevent the use of EF. Just switch to manual mode prior to closing EF, as a workaround. Randy
  3. It is not fixed by the latest alpha build released for testing yesterday. So, not resolved. ๐Ÿ˜’ Randy
  4. Apparently this will be addressed in the next update. It's not a big issue as long as you plan on running EF every time, but if not, EF should be switched to manual mode prior to closing. ๐Ÿ™
  5. Yes. But only in Manual mode. If you shut down EF from Auto mode, the dll entry remains, as do the shaders. Hopefully this will be fixed in the next build.
  6. EF removes the shader cache, not the files installed into the ShadersHLSL by Tomatoshade. You do not need to re-apply the tomatoshade profile. But, EF can alter the appearance in the sim by manipulating the shaders dynamically, and swapping textures. And see my post above if you are using EF in auto mode. You will need to delete the Shaders folder (not ShadersHLSL!!!) if not using EF.
  7. EF checks the programdata dll.xml file on launch and will add the EnvironmentForce_x64.dll entry if not found, or if found disabled.
  8. So, upon further testing, EF will delete the Shaders folder on shutdown only if Manual Mode is in use. In Automatic mode, the Shaders folder remains on shutdown. You don't even need to start P3D to test - just start EF and then create a Shaders folder, then shutdown EF in either case. Randy Further info: it also appears that your settings don't get backed up in Auto mode, even though 'Enable Automatic Backup at Closing' is set ON.
  9. Note that a clean re-install of EF v20190625 (deleting REXModules and Documents\REX 5\REX Environment Force) does not result in Shaders being deleted on EF exit. Randy
  10. I just completed another short flight. Same issue. This time I switched to manual mode then back to auto - all options were shown as 'waiting'. But the shaders remain upon closing EF.
  11. Yes. They are only deleted (the folder is deleted) on the next launch of EF.
  12. @timest999 , I just did a couple tests and the Shaders are not getting removed when EF shuts down. The first time, I closed EF a few seconds after the p3d process ended. The second time, I waited 5+ minutes before shutting down EF. The first time I closed EF before closing Active Sky. The second time, I closed Active Sky after a minute or so. Here are some screen captures: Before starting P3D: After P3D process terminated: Task Manager: There have been no app crashes showing in Event Viewer, either. Thoughts or suggestions? Randy P.S. This is using the default F22 @ KVPS Rwy 19.
  13. Thank you for this information, @timest999 . Randy
  14. Hmmm, I'm not seeing this on my system. Does it wait for the prepar3d.exe process to terminate? Perhaps I am closing EF too soon? Or is it the dll that does it? If P3D has an APPCRASH on exit, will this affect the clearing of the Shaders folder by EF? The reason I ask is that I am troubleshooting exactly that issue (APPCRASH) and I'm fairly convinced that it is an add-on that I am starting manually (Active Sky, Environment Force or Aivlasoft EFBv2, and sometimes Navigraph Charts). Randy
  15. Agreed. I suppose it would have to happen before and after. Another option is a batch file, but not an elegant solution. Randy
  16. EF deletes the Shaders folder upon launch. If you decide not to run EF, you will have to manually delete the folder (or the files inside) before launching P3D. Randy
  17. The Shaders folder gets deleted every time you start EF, so I guess it makes sense that if you don't start EF, the 'old' shaders are still there and should be deleted if you don't want to use EF. What I don't understand is why they would cause the grey scenery. I guess it has something to do with the way EF works. Also, I wasn't using Tomatoshade. I only knew it had a backup of the pertinent original ShadersHLSL files when I tried it in the past. I'm going to try it again as it's nice seeing puddles on the ground. ๐Ÿ˜Š Randy
  18. Gรฉrard, for some reason I am no longer seeing the grey textures when not using EF. All I really did was reinstall the (10 changed) stock shaders back into ShadersHLSL (I was using Tomatoshade which had a backup), disabled the EF dll in Programdata dll.xml, ran the sim without starting EF to see that everything looked fine (it did), closed sim, ran SF and installed 3D cloud model structures (not sure why but noticed I had never done this before - assumed it was automatic), ran EF (this will re-enable the dll) and made sure settings were fine and switched to auto mode, then launched the sim. Since then, I don't have grey textures when not using EF. Not sure why. I use ASP4 and leave SF closed. ๐Ÿค” Randy
  19. @timest999, I'm pretty sure we know that you need to start EF beforehand, but if you don't want to use EF (and disable the dll as well) the sim will appear gray unless you also restore the 10 modified files in ShadersHLSL (if you have a backup). Is it not possible to change this behavior so running EF is optional? Randy Edit: So, I was obviously out to lunch there. If you leave the dll enabled but do not start EF the scene isn't gray. I guess it's only if the dll is disabled. So, please disregard and accept my apologies. ๐Ÿค Edit 2: Now I can't duplicate the issue I had before. If the dll is disabled and I don't start EF, the scene is not gray. Not sure what happened, maybe it was the old build...
  20. This also occurs when you disable the dll and start the sim without EF. Using P3Dv4.5hf1. Randy
  21. Glad to help, Rick. Another option is to run P3D on your primary monitor. (Edit: oops, you already know that). Not ideal for my setup, but it does work. Hopefully the next patch will address multiple monitors. One other tip - no need to run SF after choosing your textures/theme unless you are using the weather from it. But you probably already knew that. ๐Ÿ™‚ Randy
  22. Well, you need to take a break sometime... ๐Ÿ˜‰ I'm afraid I can't offer any assistance there. I have yet to wander into the shader modding - maybe soon. I am using the latest beta of ASP4 and it seems to work as it did before, meaning I haven't noticed any issues myself. EF seems to use it to gradually change my weather visuals. Randy
  23. @RickJH Once you start the P3D scenario and get the black screen with sounds in background, press ALT (if you are in Full Screen and your menu bar is hidden) and use View menu to go back to a windowed view and drag your P3D window most of the way to your primary monitor and let go. The display should now appear (with the mini-UI), then drag the window back and go back to full screen (if that's what you use). You lose the mini-UI (support says they are working on that) but at least you can use the main UI and see how things look, which is great IMHO. Randy
×
×
  • Create New...