For some other reasons I checked my Program Data dll.xml and realized that the REX EF entry is gone. Is it possible that the latest update of REX EF did remove its own dll.xml entry?

Edited October 12, 20196 yr by Nemo

Not mine.

here is mine if you want to put it back

 

Quote

<Launch.Addon>
    <Name>REX Environment Force</Name>
    <Disabled>False</Disabled>
    <Path>REXModules\EnvironmentForce_x64.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>

 

Thanks. That's strange, because I had not recognized any issues and REX EF seemed to work as usual. How could that be without the dll.xml entry?

8 minutes ago, Nemo said:

 How could that be without the dll.xml entry?

There's another dll.xml. The REX entry may be in that one.

40 minutes ago, BillS511 said:

There's another dll.xml. The REX entry may be in that one.

No, it is not. Not sure what's going on there. Maybe I simply did not recognize that REX EF does not work properly? I have it only in Automated Mode. Before I start a FS session, I first start EF, then AS then P3D. In flight I have the EF Mini GUI which decrease to minimum. That's all what I'm doing with REX EF.

Rex EF entry is created in the dll.xml when the EF program is launched (reason why you MUST launch it before P3D) and removed when it exits (this is the solution selected by REX to solve the mini-UI error message when running P3D without EF).

So this is not an issue, but the normal behavior.

Gérard

43 minutes ago, gaab said:

Rex EF entry is created in the dll.xml when the EF program is launched (reason why you MUST launch it before P3D) and removed when it exits (this is the solution selected by REX to solve the mini-UI error message when running P3D without EF).

So this is not an issue, but the normal behavior.

Gérard

Ahh, that was it. Thank you. I knew that something had changed ... 😉