September 27, 20178 yr i see rxpGnsSim32.dll in attached module it should not be rxpGnsSim64.dll instead ? your C:\Users\<youruser>\Documents\Prepar3D v4 Add-ons\Reality XP GNS\add-on.xml" contains "C:\Program Files (x86)\Reality XP\GNS Simulation\FltSim\64" or "C:\Program Files (x86)\Reality XP\GNS Simulation\FltSim\32" folders ? if your are using P3Dv4 on Win10 64, it should be like this <AddOn.Component> <Category>DLL</Category> <Name>Reality XP GNS V2 Menu</Name> <Path>C:\Program Files (x86)\Reality XP\GNS Simulation\FltSim\64\rxpGNS2_menu.dll</Path> </AddOn.Component> <AddOn.Component> <Category>Gauges</Category> <Name>Reality XP GNS V2 Gauge</Name> <Path>C:\Program Files (x86)\Reality XP\GNS Simulation\FltSim\64</Path> </AddOn.Component> i9-10850k - Asus Tuf Z490+ - 32 Go DDR4 - RTX 3070 8Go MSI Trio X
September 27, 20178 yr @nirgal76 this is perfectly normal: the 32 bits dll is attached to the 32 bits process!
September 27, 20178 yr Further on this, and thanks to your reports, we might have found something that could lead to such logs. However, we're yet to figure out why is it only few systems are reporting this. Nevertheless, the next build might prove to solve this, and luckily, these are only logged events which aren't prohibiting the use of the GNS V2 in P3D.
September 27, 20178 yr Author 2 hours ago, RXP said: Further on this, and thanks to your reports, we might have found something that could lead to such logs. However, we're yet to figure out why is it only few systems are reporting this. Nevertheless, the next build might prove to solve this, and luckily, these are only logged events which aren't prohibiting the use of the GNS V2 in P3D. Should I then ignore the reports and press on?
September 27, 20178 yr I'd guess it is safe to pause the reports for now unless the situation on your system changes (that is the error code, or the nature of the error change).
Archived
This topic is now archived and is closed to further replies.