v27 and above - Single Player Bug/Crashes report thread

[ls612]

Last SVN (today).
I get recurrent CTD with this message:
"Failed to allocate video memory. Please try to reducing your graphic settings.
File: \main\Civilization4\SDK\Gamebryo2_0\CoreLibs\NDX9Renderer\NDX9VBManager.cpp, Line:1019"
Viewport on, default setting. Dynamic unit on.
Map size: large.
Please help! What can I do?
If useful, I can get an autosave few turns before CTD, and (if someone tell me where it i) a minidump

Comp specs and OS please?

 

[strategyonly]

Last SVN (today).
I get recurrent CTD with this message:
"Failed to allocate video memory. Please try to reducing your graphic settings.
File: \main\Civilization4\SDK\Gamebryo2_0\CoreLibs\NDX9Renderer\NDX9VBManager.cpp, Line:1019"
Viewport on, default setting. Dynamic unit on.
Map size: large.
Please help! What can I do?
If useful, I can get an autosave few turns before CTD, and (if someone tell me where it i) a minidump

Any time it CTD's just do what Post # 1 informs us to do, thx.

 

[The Boss]

OS: windows XP professional (with /3GB on)
Comp: Intel Core Quad CPU Q6700 @ 2.66 GHz 4 GB RAM 2 Video Card NVIDIA Geforge GTS 250 (1 GB RAM DDR3) in SLI

 

[matt1975]

Bombing missions with the Early Fighter also cause a CTD... Has anyone been able to corroborate or confirm the CTD with the save game I sent?

Is nobody on this? Just wondering why this is being ignored. It's making the game unplayable.

 

[ls612]

Is nobody on this? Just wondering why this is being ignored. It's making the game unplayable.

You need to post a save in which it reproduces and the minidump. See the FAQs thread for more info, but the long and the short is without those two things we can't help you.

Nevermind, I saw your original post, sorry. We aren't quite certain what is causing that, Koshling thinks it is an animation issue, but the odds of that being true given that it happens on many airplanes is low.

 

[The Boss]

Here last autosave before my CTD

 

[ls612]

OS: windows XP professional (with /3GB on)
Comp: Intel Core Quad CPU Q6700 @ 2.66 GHz 4 GB RAM 2 Video Card NVIDIA Geforge GTS 250 (1 GB RAM DDR3) in SLI

What are your Viewport sizes? Because you will get less memory with the 3GB switch than having a 64 bit OS would give. I'd suggest no bigger than 45 by 30 and graphics at medium as a max for your rig. However it is certainly possible to run C2C on something like that, I ran it for a year on a rig much worse than that.

 

[The Boss]

Viewport 40 x 40 focus border 2

 

[The Boss]

Thanks ls612!
Lowering viewport size to 30 x 30 I get no more CTD with same autosave.
I also lowered resolution to medium.
You saved my last game!

 

[Koshling]

Nope... Very repeatable issue, occurs also with the IL2 so according to your theory its not necessarily an animation issue. Other aircraft (ornithopter, autogyro) I have don't have the recon option. I have attached a copy of my save game. Just look for an Early Fighter or IL2 and give it a go. Push the recon button and then click on the map to dispatch. My game (now svn4329) crashes very consistenly when trying to do this. Please let me know what your findings are.

FINALLY pinned this down (it was a SLOW process!). It was down to some changes made in a combatMod update in rev 4203. Fix will be on the SVN shortly.

@Thunderbrd: you must never change the signature of a method declared as DllExport since those are function as the game engine calls, and if you change the signature it will throw a procedure-not-found exception when it tries to bind to it. In this case you changed getBestDefender() so that some of its parameters ceased to be declared as 'const'.

The reason you found it convenient to do this was ultimately because a bunch of methods you added (such as withdrawVSOpponentProbTotal()) took parameters they had no intention of modifying, but didn't bother declaring those parameters as const, so you found you got errors when you tried to call them from other methods that DID declare the things you wanted to pass as parameters as const. Removing all the 'const' declarations (even if you didn't have the killer issue of that changing an externalized signature) is going to be the wrong approach in 99% of all cases - the first thing you should ask yourself is 'why can't this be const?' (i.e. - am I really doing something that should modify it?). If there is no good reason why it cannot be const it almost certainly should be.

Edit - @SO - this also explains your recent minidumps

 

[Lexotan_sedlex]

The portrait painter building uses the OLD_DYE tag.

 

[Vokarya]

The portrait painter building uses the OLD_DYE tag.

That's my building -- I'll fix it tomorrow when I get to my main computer (I'm traveling right now.)

 

[strategyonly]

FINALLY pinned this down (it was a SLOW process!). It was down to some changes made in a combatMod update in rev 4203. Fix will be on the SVN shortly.

Edit - @SO - this also explains your recent minidumps

Oh my goodness, thank you sooo much, it was heck playing with Viewports and getting a CTD every now and then, now PLS on to the arrow problem (hint hint) (jj)

 

[Lexotan_sedlex]

http://upload.crazzy.com.br/show-image.php?id=ff2f67eb160a4e03991887c8b396a24f


Hello, the priests are not assembling together.

 

[strategyonly]

http://upload.crazzy.com.br/show-image.php?id=ff2f67eb160a4e03991887c8b396a24f


Hello, the priests are not assembling together.

DID you change a few things around, because i dont remember having put back in the slider?

 

[astrohawke]

Can't progress past this point. Game crashes every time I end turn. Haven't updated SVN since V27 release I think. I can try updating but I dislike getting random changes halfway through a game, particularly potentially unstable ones. Please let me know what the problem is and whether you can progress or not. Thanks.

Any help please?

 

[strategyonly]

Any help please?

See post # 1 pls, then respond back, thx.

 

[astrohawke]

See post # 1 pls, then respond back, thx.

All the files are in the original post

 

[JosEPh_II]

All the files are in the original post

If you look at your post with the save, it's been d/l'd 10 times now which means at least several ppl are looking at it.

Did the zip contain the Minidump too?

JosEPh

 

[Thunderbrd]

@Thunderbrd: you must never change the signature of a method declared as DllExport since those are function as the game engine calls, and if you change the signature it will throw a procedure-not-found exception when it tries to bind to it. In this case you changed getBestDefender() so that some of its parameters ceased to be declared as 'const'.

The reason you found it convenient to do this was ultimately because a bunch of methods you added (such as withdrawVSOpponentProbTotal()) took parameters they had no intention of modifying, but didn't bother declaring those parameters as const, so you found you got errors when you tried to call them from other methods that DID declare the things you wanted to pass as parameters as const. Removing all the 'const' declarations (even if you didn't have the killer issue of that changing an externalized signature) is going to be the wrong approach in 99% of all cases - the first thing you should ask yourself is 'why can't this be const?' (i.e. - am I really doing something that should modify it?). If there is no good reason why it cannot be const it almost certainly should be.

I just looked at your change there and I fully understand what you mean. I apologize for that poor decision. I had thought if it would manifest as a problem it would've done so more immediately but I can see how and why I was wrong. I felt guilty as soon as I noticed the change - and truth be told, what you did to fix the problem was epically easier than the headache I went through trying to fix it.

Now if I could only figure out what the hell I'm doing wrong with this savegame compatibility!!!

I'm frustrated to wit's end here with this! I've spent all day scouring through every change looking for something somewhere that might account for the problem and I still can't seem to find it. I'm updating the branch though so that some known issues that have been fixed remain so if you're taking a look.