G3D.DLLerror with latest fsuipc 4.939n/m

[stuarth]

Pete,
Not sure if at fault but since updating to fsuipc 4.939m then ....n, I seem to be getting a g3d error whenever I try to load a flight from the FreeFlight screen. I looked at the fsuipc log file, and there is no mention of it loading the g3d monitor line as there used to be in earlier versions.

Is there a way of checking that your g3d fixes are working?

Thanks
Stuart
Dowson *********
Reading options from "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 7
Module base=56F00000
User Name="STUART HYETT"
User Addr="deleted by forum mod"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
812 System time = 08/05/2015 17:14:21
812 FLT path = "C:\Users\Stuart\Documents\Flight Simulator X Files\"
874 Trying to connect to SimConnect Steam ...
905 FS path = "C:\Program Files (x86)\Steam\steamapps\common\FSX\"
983 LogOptions=00000000 00000001
983 --- CONTROLS timer memory location obtained ok
983 --- SIM1 Frictions access gained
983 --- FS Controls Table located ok
983 --- Installed Mouse Macro hooks ok.
983 --- Wind smoothing fix is fully installed
983 SimConnect_Open succeeded: waiting to check version okay
999 Trying to use SimConnect Steam
3245 Running in "Microsoft Flight Simulator X", Version: 10.0.62613.0 (SimConnect: 10.0.62613.0)
3245 Initialising SimConnect data requests now
3245 FSUIPC Menu entry added
3292 C:\Users\Stuart\Documents\Flight Simulator X Files\FLYUK.FLT
3292 C:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\mjc8q400\MJC8Q4.air
18689 C:\Users\Stuart\Documents\Flight Simulator X Files\FLUK8.PLN
18689 Weather Mode now = Custom

[Pete Dowson]

Not sure if at fault but since updating to fsuipc 4.939m then ....n, I seem to be getting a g3d error whenever I try to load a flight from the FreeFlight screen. I looked at the fsuipc log file, and there is no mention of it loading the g3d monitor line as there used to be in earlier versions.

 

Your G3D error will not have been the one FSUIPC used to trap -- that one is fixed in the version of FSX-SE you are using, which is why FSUIPC doesn't attempt to trap it.

 

You need to report your different one to DTG support. Send them the MDMP file you should find in the FSX folder. Send to dtgflightsupport@dovetailgames.com

 

Pete