rgl error

[Lamey]

I keep getting intermittent crashes with the message:

RGL ERROR
Unable to restore vertex buffer.

I've looking around for any solutions but I'm not seeing any (any that actually work anyway)

I played native for a while to check and I got no crashes after a few hours of playing, whereas I can barely get through a battle in SOD without a crash.  I crash during battle often, also during the scene transitions in sieges, sometimes when talking to a council member and occasionally when I try to save.  It's always the same message.

I have my graphics options set pretty modestly - battle size 100 (I play warband with it set to ~500), no corpses, no AA.

 

[Vercingetorix]

It's always been that way with SoD.

I've had the same experience as you. I can play with 500 at least in WB with no problems. It's something to do with SoD's textures.

I set the bodies to 0 and the textures to about 70 and it plays fine with 150 battle size. It might be different for other people, but I've found that the "texture quality" makes the most difference.

 

[Lamey]

I'll give that shot thanks.

 

[kaze-yaida]

The glitch you have is actually an overload. It happenes when the amount of textures the game is loading becomes so hgue it cant keep up and the game failed to load a vertext on time causing the game to crash.

Just tone town the graphics and youll be fine. This cna be done with amount of units or textures.
I have a pretty middle class to low class computer and 200 battle size with max options works just fine for me.(thank you LOD models!)

 

[Lamey]

Well I run Warband on much much higher settings with no trouble.

That said, so far turning the texture detail down to 70 seems to be working.  I played for a few hours with no crashes. (added bonus, I can't tell the difference visually)

 

[kaze-yaida]

Warband uses much less textures, higher details MDOELS but different textures. SOD runs multiple textures quite often and many different ones even among the same troops

SOD also deals with AI, formations, adding in some people love to use the 300-400 battlesizer for some reason.(Max 400 troops, even more when outnumbereD? might as well play Team fortress 2 with 50 people)

 

[Lamey]

Warband uses much less textures, higher details MDOELS but different textures. SOD runs multiple textures quite often and many different ones even among the same troops

SOD also deals with AI, formations, adding in some people love to use the 300-400 battlesizer for some reason.(Max 400 troops, even more when outnumbereD? might as well play Team fortress 2 with 50 people)

Well the one thing I have to bring up here: I was getting the same crash just from talking to my council.  Loading up the castle scene with 4 or 5 dudes in it shouldn't come anywhere near using available texture memory.  Not to mention getting the crash after saving, or while looking at my camp menu.  It seems like there is some more specific bug that's being triggered.  To be clear it did not always crash: I could go through a 3 phase battle scene with battle size at 200 and 4x AA on with no problem, only to have the game crash while I was talking to my marshal afterward.

I did find a few posts on other boards saying its a compatibility problem with newer ATI cards, but they didn't include any solutions.

Side rant that is so off-topic that I decided to spoiler it:

Spoiler

I really only started turning my battle sizer up because of some of the ridiculously sized warparties in some mods. 

Theoretically you could get a huge multi-lord cluster... thing... in native M&B, but as far as I've seen those big marshall led packs tend to scatter when they get to close to one another.  Each individual lord evaluates the massive horde he's up against and flees.

I think it was Prophecy of Pendor where I had to deal with a boss spawn with 1700 troops in a single party.  Fighting a 3000 troop battle 100 troops a phase is not fun.

Big battle sizes definitely skew the balance, the larger the battle size the less awesome cavalry is it seems.  In native I don't think that's such a bad thing sometimes.  There's really nothing you can't pulverize with a full party of Swadian knights (in the field that is) and the battle round setup favors top tier troops because it minimizes the ability for lower tier troops to wear them down. (I'm pretty sure any non-hero unit that isn't incapacitated is fully healed between phases).  Big battle sizes massively favor the defender in siege battles though.

Anyways, thanks again.  I played another ~3 hour session with no crashes.

 

[Cyclohexane]

Warband uses much less textures, higher details MDOELS but different textures. SOD runs multiple textures quite often and many different ones even among the same troops

SOD also deals with AI, formations, adding in some people love to use the 300-400 battlesizer for some reason.(Max 400 troops, even more when outnumbereD? might as well play Team fortress 2 with 50 people)

The Warband textures (.dds files) are identical to M&B textures.  I also would not say that Warband has more detailed models than SoD (the tri count on some items had to be lowered to increase performance).  As a matter of fact, I used many of the same Native models and retextured and saved with the same compression. 

The big difference and what you highlighted on, is that SoD uses a lot more resources.  Instead of 1 new faction like Warband, we added 13 new with countless more random mercenary troops as well.  I know I can improve performance by combining more similar troops textures mapped to the same texture file.  So when these troops come to battle, only a handful of textures need to be loaded for each item.  As a side note, I have done this for many items in 5.0 already, but to complete would require a huge job.  I have other responsibilities and I've already invested hundreds of free hours (if not more).  My suggestion for moderate to low end computers (even guys that think they have a top end computer) is to lower textures.  It is a simple fix and barely noticable. 

If we would not have added all the .lods to the models, many more people would be getting RGL errors (for example V4.5).  There is no easy solution for many players.  It is either enjoy the variety and deal with occasional crashes or lower textures. 

 

[kaze-yaida]

This is the first im hearing of the crash since LODs even came out so I dont think you need to worry.

I'm just amazed how much work you pulled getting LODs this fast.