smooth as Crisco butter.

 

 

Crisco, make butter ???

 

Damn and i've been usnig Oil all this time.

i found a 100% reproducible g3d.dll crash it looks like it might be in the same offset each time as well. goes away when i remove ftx england or use the default cessna instead of 777.  (to see the crash take off in 777 from egll, runway 27L compton 3g departure, will blow up within a few nm away from the airport every time.. doesn't happen with FTX global, but does if you enable hybrid or eu region)

 

naturally the only 'real' solution i could find for it was threads pointing to pete's fix from a few years ago hehe. no idea if this is just a matter of patching out each new offset that shows up or what.

 

sorry to hijack on this thread but since pete is lookin at it i figured that was good of of a place as any. help me obi wan dowson, you're my only hope!

 

cheers y'all

-andy crosby

 

--------------------------------

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd

Exception code: 0xc0000005

Fault offset: 0x000c7c0a

Faulting process id: 0x2844

Faulting application start time: 0x01d039bfc7bde7ea

Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll

Report Id: badeb191-a5b4-11e4-889f-e0cb4e2c4e6f

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd

Exception code: 0xc0000005

Fault offset: 0x000c7c0a

Faulting process id: 0x544

Faulting application start time: 0x01d039bcae2abc2d

Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll

Report Id: f307e0bb-a5b2-11e4-889f-e0cb4e2c4e6f

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd

Exception code: 0xc0000005

Fault offset: 0x000c7c0a

Faulting process id: 0x2730

Faulting application start time: 0x01d0393989215598

Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll

Report Id: 3978eabd-a52f-11e4-889f-e0cb4e2c4e6f

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd

Exception code: 0xc0000005

Fault offset: 0x000c7c0a

Faulting process id: 0xc58

Faulting application start time: 0x01d0393597f60a94

Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll

Report Id: 1cf52dd2-a52c-11e4-889f-e0cb4e2c4e6f

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd

Exception code: 0xc0000005

Fault offset: 0x000c7c0a

Faulting process id: 0xc58

Faulting application start time: 0x01d039316407ef13

Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll

Report Id: 685f9133-a527-11e4-889f-e0cb4e2c4e6f

----------------------------------------

Thanks, Pete. I need to purchase your product but somehow or the other never ever get around to it. Maybe it is high time now.

 

Don't buy it specifically for this "fix" as I've just learned that it may not work. It might merely succeeds in moving it on a bit. If so, then the corruption is too serious for my simple workaround I'm afraid.

 

for those already registered it might be worth persisting with the fix enabled. See more below.

 

Pete

Thanks. I just tried test version "g", Win 8.1, DX10, no manual tweaks applied to fsx.cfg, with the default Cessna 172 and OpusFSI for weather. I flew 35 minutes and then CTD:

 

You appear to still be using the original FSX-SE release from last December! (build 62607). My fix won't have any chance to work on that. It will only patch into 62608 version Terrain.DLL.

 

How is it you didn't get the update installed?

 

If you run the up-to-date FSX-SE, then it will be still worth keeping the TERRAIN patch enabled in FSUIPC, even though, as I said above, it is looking doubtful that it fixes it. I really won't know until someone does a SUCCESSFUL flight and can check in his FSUIPC4.LOG file that FSUIPC4 did actually trap and stop a TERRAIN crash. (Just search for TERRAIN in the Log file after FSX-SE is closed).

 

Pete

This is NOT the case with original FSX. If no AM is set in FSX.cfg, then no affinity mask entry appears in the Couatl program tweak screen.

No, it's the same in FSX. The Affinity mask tweak in the Addon Manager screen will always appear, regardless of the version of the sim or if the settings is present in the FSX.CFG or not.

 

The only difference between FSX and FSX:SE, is the default value used internally by FSX when there's no setting.

 

In FSX, the default value is the same as the OS value, which is "use all cores", which translates into a 15 on a quad core system.

 

In FSX:SE the default is 14, which means "use all cores except the 1st"

 

In the Addon Manager, even in FSX, if there's NO pre-existing entry, the value is 14, but that doesn't mean the tweak is already applied. It only means that IF you press the "Save to FSX" button, 14 is the value that WILL be saved there, and it will used starting on the next restart. We set it to 14 by default (when there's nothing in the FSX.CFG) because it's universally considered to be the best value on a quad-core system but again, is NOT applied until you SAVE the settings.

 

So, the only difference, between FSX and FSX:SE, is the default value used when there is not setting in the FSX.CFG.

 

i found a 100% reproducible g3d.dll crash it looks like it might be in the same offset each time as well. goes away when i remove ftx england or use the default cessna instead of 777.  (to see the crash take off in 777 from egll, runway 27L compton 3g departure, will blow up within a few nm away from the airport every time.. doesn't happen with FTX global, but does if you enable hybrid or eu region)

 

naturally the only 'real' solution i could find for it was threads pointing to pete's fix from a few years ago hehe. no idea if this is just a matter of patching out each new offset that shows up or what.

 

It isn't "patching out offsets" but hooking code into them to pre-check a pointer before it is used to make sure it won't crash the system when it is used.

 

Of all the G3D crashes folks had in FSX, there was only one which was patchable in this way. The others were more like the FSX-SE Terrain.DLL crash which I tried to patch and have now found it mrely moves the crash location.

 

However, I'll take a look at your G3D one when I get time. It won't be today I'm afraid.

 

Please report it on the Steam forum as well though.

 

Pete

If this terrain.dll error becomes un fixable, it could render SE unusable. I have not done a flight in the 777 yet, so have not pushed any boundary's yet as I have been re installing. I hope I have not just wasted 3 weeks of my life

Mind you, I think everyone should make sure you are all on the latest SE version, and you have verified the integrity of game cache if you have to.

I've run multiple long flights on FSX-SE without any CTD.

 

The only difference I see is I'm still running somewhat moderate settings and not going to the right on all the settings.  I've also only loaded base global scenery just to ease into it for now.

 

Not sure if that helps but I've had no crashes with the sim in the 777. 

 

 

I flew 35 minutes and then CTD:

Just having purchased the full version FSUPIC4 and registered it, this is not good reading. Maybe this will stall simmers from making the switch? So, the new code has still the old code's bugs!

 

 

If this terrain.dll error becomes un fixable, it could render SE unusable.

Julian, you could well be the harbinger of bad news if that happens.

 

 

Julian, you could well be the harbinger of bad news if that happens.

Hope not Rick. I will be testing proper on Thursday, and then I will know if a verify game cache fixes the problem.

If this terrain.dll error becomes un fixable, it could render SE unusable. 

 

I think that's a rather over the top reaction. There seems to be many more folks flying good and long flights without this crash than with.

 

I don't think it's a new problem with FSX-SE, i think it is just that with the improvements in both performance and VAS usage folks are winding up the settings more, and it is this which is revealing more bugs in the base FSX code similar to those which also caused a lot of the unpatchable crashes in FSX (eg the many G3D ones which FSUIPC did not patch).

 

At least there is a chance (though may be a small one) that given enough evidence DTG could fix this. There was no chance of MS ever fixing it.

 

Pete

 

 

think that's a rather over the top reaction. There seems to be many more folks flying good and long flights without this crash than with.

I agree Pete, it probably is. I was just panicking after spending many hours installing new HDD and of course W7 and FSX. The older I get, the more I tend to panic

No, it's the same in FSX. The Affinity mask tweak in the Addon Manager screen will always appear, regardless of the version of the sim or if the settings is present in the FSX.CFG or not.

 

The only difference between FSX and FSX:SE, is the default value used internally by FSX when there's no setting.

 

In FSX, the default value is the same as the OS value, which is "use all cores", which translates into a 15 on a quad core system.

 

In FSX:SE the default is 14, which means "use all cores except the 1st"

 

In the Addon Manager, even in FSX, if there's NO pre-existing entry, the value is 14, but that doesn't mean the tweak is already applied. It only means that IF you press the "Save to FSX" button, 14 is the value that WILL be saved there, and it will used starting on the next restart. We set it to 14 by default (when there's nothing in the FSX.CFG) because it's universally considered to be the best value on a quad-core system but again, is NOT applied until you SAVE the settings.

 

So, the only difference, between FSX and FSX:SE, is the default value used when there is not setting in the FSX.CFG.

Thanks for the clarification. I thought that the manager was showing tweaks which already exist, rather than ones which could potentially be applied. It does (in SE) also show HIGHMEMFIX=1 as being true, and that one at least (according to DTG) is now permanently "on" within FSX.exe without the need to specify it in the config.

@ Pete

 

I noticed that also. That's why I noted in my first post that I "checked the integrity of the game cache" before my second round of testing. But you're correct unfortunately... Same error with a CTD after about an hour and ten minutes.

I thought that the manager was showing tweaks which already exist, rather than ones which could potentially be applied.

That what it does. If the tweak exists, it will display its existing value. But if the tweak doesn't exist, it will not be hidden from the tweaks section.

 

Now, if a tweak doesn't exists in the FSX.CFG, it doesn't mean FSX it's not already using an internal default value. So, in MOST of the cases, when a tweak doesn't exist, what you see in the Addon Manager is the default value already used internally by FSX, so it won't make any difference when saving.

 

The Affinity Mask, instead, was set by default to what is being considered the best value for FSX so, in THIS case, the Addon Manager "default" (lacking a specific setting in the FSX.CFG) it's not the same as the FSX "internal default", but it's supposed to be better IF YOU SAVE IT

 

It does (in SE) also show HIGHMEMFIX=1 as being true, and that one at least (according to DTG) is now permanently "on" within FSX.exe without the need to specify it in the config.

Same as above, the highmemfix tweak is another tweak that, missing any value in the FSX.CFG, has been set to be enabled in the Addon Manager, because it's 100% sure it will a better setting. Again, IF YOU SAVE IT. Nothing is changed, until you save the settings.

 

The only difference between FSX and FSX:SE in this case, is that what the Addon Manager considered a "better default" in FSX when an explicit tweak is missing, is now an ACTUAL default in FSX:SE so, it's already working and applied, even if you don't Save it in the Addon Manager.

 

 

i think it is just that with the improvements in both performance and VAS usage folks are winding up the settings more

 

There was no chance of MS ever fixing it.

Very good points, Pete.