Jump to content
Sign in to follow this  
robwallyh

CLOSED Uninstalled until HDR unlocked and role of Active Sky clarified

Recommended Posts

I am afraid I am with @Nemo and others on this one. I have supported REX for many years, and enjoy Sky Force, and this post is not at all intended to denigrate REX's valiant efforts, or their very ambitious EF product,  but this is my experience so far....

Initial Install went OK, but like many I did not enjoy the brightness and overdone bloom. OK could control that through the mini UI. Installed the Tech Update and was able to use Tomato shade and not get greyed-out cockpits (I want to use TS for aircraft reflections on non-PBR enabled models).

Then last night I decide to try run P3D (on 4.4 client as I await LM 4.5 FPS fix), just fly and NOT test or run EF. But EF's brightness/bloom settings remained "locked in" and the P3D internal HDR sliders do nothing (/graphics/lighting, HDR on and tried set saturation to 0, which should give a monochrome view, but it stays fixed as set by EF).

So restart computer and same. Try another run with EF, and last straw, mini UI is gone.

So I uninstalled EF, rebooted, reset the Shaders HLSL from backup, cleared shader cache, ran P3D and happy days, could again control HDR brightness, bloom and saturation from P3D graphics/lighting UI. Closed, reinstalled Tomato Preset RD1.7 and am back to SF3D + ASP4 + TS.

Along the way my GSX stopped working and in investigating that I found that an entry in ProgramData/ Lockheed Martin/ Prepar3d V4/ dll.xml referring to a REX EF module DLL had been left behind, despite the uninstall.  Is it this entry that locks the EF HDR settings into P3D even when EF is NOT running?. If EF is uninstalled the REX dll referred to in this dll.xml is gone so it cannot load, and one is back to a straight P3D setup. 

But why, oh why not clean up the dll.xml on uninstall, and even more importantly, set the dll entry to not initialize the REX module if EF is NOT run, so users have the option to run a EF-less setup if they wish. 

Many agree with me in this forum and over at Avsim that Environment Force should not take control of P3D settings such that when EF is not running one is still stuck with its HDR settings.

I also cannot confirm if the automated cloud morphing and  lighting dynamics work if using ASP4 for the weather engine. Have not seen anything change. Admittedly one needs a very dynamic weather situation to test under. But what concerns me is that the METAR information reported in the auto EF interface when running ASP4, and with EF weather smoothing and NOAA data read OFF as advised if using ASP4, is non-sensical except for the temp/dewpoint and QNH readings at the end of the string. If this is what is reported to screen then I am seriously left wondering what values of cloud types, levels and densities are being used to model cloud morphing and lighting! Switch to read real time weather from NOAA and this METAR report makes sense. Maybe Active Sky is compatible with EF, but that does not necessarily mean it will work just as well to control auto-mode as when using REX's SF weather engine / NOAA data. Some real clarification about the EF-ASP4 interaction by REX developers would be appropriate.

The lack of correct low visibility settings / fog when using ASP4 and with EF weather smoothing off (automation mode) also indicates to me that weather injected into the sim by ASP4 is not being read correctly and being used by EF to set up the correct "environment " look in the sim. Unless one toggles the fog mode to off in the mini UI (manual intervention in an automated mode!?).

Maybe if one uses the SF weather engine this all works perfectly, but I have never been a fan of that weather engine because;

  1. Historical weather cannot be used
  2. I have a serious problem with REX's wind interpolation model, since REX Essential days. HiFi have this aspect (maths) spot on.

So for the foreseeable future EF stays off my computer. Maybe when WeatherForce is released and I see that it is at least up to HiFi standards I will give it another try.

  • Sad 1

Share this post


Link to post
Share on other sites
1 hour ago, robwallyh said:

I am afraid I am with @Nemo and others on this one. I have supported REX for many years, and enjoy Sky Force, and this post is not at all intended to denigrate REX's valiant efforts, or their very ambitious EF product,  but this is my experience so far....

Initial Install went OK, but like many I did not enjoy the brightness and overdone bloom. OK could control that through the mini UI. Installed the Tech Update and was able to use Tomato shade and not get greyed-out cockpits (I want to use TS for aircraft reflections on non-PBR enabled models).

Then last night I decide to try run P3D (on 4.4 client as I await LM 4.5 FPS fix), just fly and NOT test or run EF. But EF's brightness/bloom settings remained "locked in" and the P3D internal HDR sliders do nothing (/graphics/lighting, HDR on and tried set saturation to 0, which should give a monochrome view, but it stays fixed as set by EF).

So restart computer and same. Try another run with EF, and last straw, mini UI is gone.

So I uninstalled EF, rebooted, reset the Shaders HLSL from backup, cleared shader cache, ran P3D and happy days, could again control HDR brightness, bloom and saturation from P3D graphics/lighting UI. Closed, reinstalled Tomato Preset RD1.7 and am back to SF3D + ASP4 + TS.

Along the way my GSX stopped working and in investigating that I found that an entry in ProgramData/ Lockheed Martin/ Prepar3d V4/ dll.xml referring to a REX EF module DLL had been left behind, despite the uninstall.  Is it this entry that locks the EF HDR settings into P3D even when EF is NOT running?. If EF is uninstalled the REX dll referred to in this dll.xml is gone so it cannot load, and one is back to a straight P3D setup. 

But why, oh why not clean up the dll.xml on uninstall, and even more importantly, set the dll entry to not initialize the REX module if EF is NOT run, so users have the option to run a EF-less setup if they wish. 

Many agree with me in this forum and over at Avsim that Environment Force should not take control of P3D settings such that when EF is not running one is still stuck with its HDR settings.

I also cannot confirm if the automated cloud morphing and  lighting dynamics work if using ASP4 for the weather engine. Have not seen anything change. Admittedly one needs a very dynamic weather situation to test under. But what concerns me is that the METAR information reported in the auto EF interface when running ASP4, and with EF weather smoothing and NOAA data read OFF as advised if using ASP4, is non-sensical except for the temp/dewpoint and QNH readings at the end of the string. If this is what is reported to screen then I am seriously left wondering what values of cloud types, levels and densities are being used to model cloud morphing and lighting! Switch to read real time weather from NOAA and this METAR report makes sense. Maybe Active Sky is compatible with EF, but that does not necessarily mean it will work just as well to control auto-mode as when using REX's SF weather engine / NOAA data. Some real clarification about the EF-ASP4 interaction by REX developers would be appropriate.

The lack of correct low visibility settings / fog when using ASP4 and with EF weather smoothing off (automation mode) also indicates to me that weather injected into the sim by ASP4 is not being read correctly and being used by EF to set up the correct "environment " look in the sim. Unless one toggles the fog mode to off in the mini UI (manual intervention in an automated mode!?).

Maybe if one uses the SF weather engine this all works perfectly, but I have never been a fan of that weather engine because;

  1. Historical weather cannot be used
  2. I have a serious problem with REX's wind interpolation model, since REX Essential days. HiFi have this aspect (maths) spot on.

So for the foreseeable future EF stays off my computer. Maybe when WeatherForce is released and I see that it is at least up to HiFi standards I will give it another try.

I am trying to help you here. Let's focus on EF features.

First, HDR. You can always change the EF HDR off.

But if you are using it, can you post an image of what is going on?

Then, we will focus on the other issues.

Thanks,

Federico

Share this post


Link to post
Share on other sites

Thank you for your response Federico

I have  uninstalled Environment Force so cannot give you screen shots of EF HDR off. I was well aware that you can turn EF enhanced HDR off or change EF HDR parameters via the mini UI. That was NOT my problem.

I uninstalled EF because it "took over" my sim settings (disabled P3D internal lighting settings) even when EF is NOT started for a session. Due to an entry in programdata/dll.xml EF is actually always running. Sure a user can turn this off by manually editing the dll.xml, but I feel it is programmatically more correct, quicker (and polite) for REX to automatically switch their dlll off on exiting EF.

Many users on this forum and over at Avsim are having issues related to this inability to switch off EF. I am only trying to help by suggesting REX disable EF fully on exiting the interface. 

Until it is confirmed that this is done I will not re-install EF. I simply do not allow any software to run uncommanded on my PC, or to make changes to files that I am not made fully aware of.

Thanks

Rob (Alias geolpilot on  Avsim and Discord)

 

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • See our many awards!

×
×
  • Create New...