May 19, 201214 yr Commercial Member Well, this has been a first since the fix by Pete Anyone else getting these crashes back? Also the log is not stating how many errors it captured, it used to! Flying in same areas, EGBB Clive Clive Joy
May 19, 201214 yr Commercial Member Well, this has been a first since the fix by Pete There are lots of possible crashes in G3D.DLL, as you'll see if you scan through the original thread. FSUIPC only patches one specific one. I did look at a couple of the others but they weren't patchable in any way that wouldn't compromise the session. It was just pure luck that the most common one was okay to patch without evident consequences. Also the log is not stating how many errors it captured, it used to! The log should contain two lines referring to G3D even if it failed to trap any: 4610 G3D.DLL fix attempt installed ok near the beginning, and G3D fix: Passes 13045, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 43 Allocs, 43 Freed ********* FSUIPC Log file closed *********** at the end, assuming it got to a normal close. Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
May 19, 201214 yr Author Commercial Member Thanks Pete That's why I didn't see the normal last log bit, as it CTD Clive Joy
Create an account or sign in to comment