POLL: ATI card owners with drivers 10.7 or higher -- Graphics issues (WB 1.132)?

Do you have graphics issues with ATI drivers version 10.7 or higher (WB 1.132)?

  • Yes, I (sometimes) have invisible textures, distortions, etc.

    选票: 7 63.6%
  • No, I don't have any graphical issues at any time (so far).

    选票: 4 36.4%

  • 全部投票
    11
  • 投票关闭 .

正在查看此主题的用户

I updated the title and the first post with the following:

Current best fix for this issue has been provided by Edwardecl:

Open the file game_variables.txt (in for example C:\Program Files (x86)\Mount&Blade Warband\Modules\Native) and set the line:
new_buffer_size_regular_static          = 131072
to:
new_buffer_size_regular_static          = 196608



This is the best fix so far because it causes minimal changes to the settings and it fixes the graphics issues.


Update:
Unfortunately the above fix still yields some issues with graphics.
I tried an MP map and saw sky boxes on the ground instead of normal ground.

So far the alternative best fix (at least for me) is to comment away all buffer_size lines.
 
I probably would have these issues if my driver installer didn't crash every time I tried to run it. Very annoying. But since I don't have these drivers, I'd like to say I'm running on ATI video card with no issues! Hah.
 
Yeah forget my previous post. played it for an hour or so and the problems return, even if I make every value higher it only delays the problem.

Does just removing the values fix it at all? or is it the same? I might just do that.
 
edwardecl 说:
Yeah forget my previous post. played it for an hour or so and the problems return, even if I make every value higher it only delays the problem.

Does just removing the values fix it at all? or is it the same? I might just do that.

So far I have not encountered any graphics issue while having removed all the buffer_size lines.

I have logged over 4 hours and it seems stable and without issues, so I think removing those lines is a good temporary fix until Taleworlds fixes whatever they have going on in their rendering system.
 
[quote author=serdar]no, engine uses default values if you do not specift them.[/quote]

On the bugs forum Serdar just confirmed that leaving the buffer_size values out will have the effect of the engine using its default values.

So, since the engine's default values seem much better than the game_variables.txt, I think commenting them out is the best way to go for now.
 
Treebeard 说:
Silentspy 说:
tried that "fix" and the game is just very sluggish now however the bugs are fixed but i rather prefer a non sluggish game and older ati drivers..

These buffers are the same that caused RGL errors in M&B (at least in some mods for ATI cards). That's interesting.

By the way, another "fix" is to just comment away all buffer size lines like this (put a # before each line):
插入代码块:
#new_buffer_size_dx7_regular_ffp_static  = 262144
#new_buffer_size_dx7_regular_ffp_dynamic = 262144

#new_buffer_size_regular_ffp_static 		=  32768
#new_buffer_size_regular_ffp_dynamic     =  32768
#new_buffer_size_regular_static          = 131072
#new_buffer_size_regular_dynamic         =  65536
#new_buffer_size_skinning_static         = 131072
#new_buffer_size_skinning_dynamic        =  65536
#new_buffer_size_normal_map_static       = 131072
#new_buffer_size_normal_map_dynamic      =  65536
#new_buffer_size_normal_map_skinning_static  = 131072
#new_buffer_size_normal_map_skinning_dynamic =  65536

Be sure to back up the original game_variables.txt just in case.

I tried by commenting out all buffer_sizes and the result is that I don't get the texture glitches and as far as speed is concerned it did not affect the game performance negatively.

However, I didn't test long enough to see if the game performance would decrease after more game time had passed.

Also, I'm not sure if there are other side effects that may occur, so test it at your own risk.


Edit:
After one hour and a half of Multi Player gaming, it still seems to work without any issues or slowdowns.
I think I've logged 2 hours without noticing any side effects now. All textures work normally and no distortions or flickering or anything bad has happened, so it definitely seems to be fine without the buffer_size lines in game_variables.txt.

Yes, this seems to be working for me for now, over 8 hours straight with no anomolies - I have had several crashes, but I think they are unrelated.  So thanks for sharing this! (Radeon 5870 with catalyst 10.9 drivers. i7 920 6GB Ram on win7.)
 
Mr.Pibb 说:
Yes, this seems to be working for me for now, over 8 hours straight with no anomolies - I have had several crashes, but I think they are unrelated.  So thanks for sharing this!

Thanks for the testing! I'm going to tentatively update the title and the initial post.

Hopefully more people will test the settings out and hopefully it will solve their graphics issues as well.
 
I wondered why my game was spazzing out, been like it since 10.7 to 10.9 on my HD5770 1GB. Commenting away the buffer thingamabobs seems to have worked, just had a 3 hour stretch on single player with no issues. :3

Dunno why I keep buying ATI cards; last one was overheating and this one breaks my beloved Warband as well as delaying my boot-up. Ah, if only Nvidia weren't complete bastards.
 
Dz6KC.jpg

ppLiZ.jpg


Commenting out all those buffers did not change a thing, its still quite horrible.

OP: Link to bugtracker post in first post should be there.
 
del_diablo 说:
Commenting out all those buffers did not change a thing, its still quite horrible.

OP: Link to bugtracker post in first post should be there.

Do your graphics issues disappear if you use ATI drivers 10.3, 10.4 or 10.5?

If they do not disappear when using those drivers, you have an issue that is not covered by this thread.

For me at least I can confirm that the issues go away when using the engine's default values (i.e. when removing/deactivating the buffer_size lines).

(Also make sure that you're deactivating the game_variables.txt buffer_sizes for the right module if you are playing a module that is not native.)
 
Ryantheskinny 说:
After commenting out all the buffers i seem to be getting RGL errors now.  :cry:

Yes, that may be a side-effect on some systems (especially if you have a big party and are many days into the SP campaign). I haven't had them in Warband so far, but the buffer_size lines in M&B original did cause RGL errors in at least some mods (and also probably native). This means that the default engine values may fix one thing (the graphics) but cause another thing (RGL errors).

Do you have the Battle Sizer installed. If you do, try lowering the units on the battlefield to maximum 150.
Also, try lowering corpses to 0 and rag dolls to 0 and see if that helps your RGL errors.

By the way, what kind of RGL error is it?
Is it "Unable to restore Vertex Buffer"?

Edit:
Also, if you have removed your System Page File, please try putting it back to 1.5*Installed RAM.

Edit2: Updated first post to reflect this issue.
 
I just feel I need to comment on the 1.5x number. This used to be the standard before we had loads of ram in our computers. And if you have 2 gig ram or less you could do well with that number. I ran a 6 gig system with 3072 mb swapfile for years with no issues at all. So if you have 8 gig of ram, there is really no need for a 12 gig swapfile :smile: But a 3 gig would certainly not hurt, and we usually have room for that anyways. There are lots of documentation about this on the 'net, just Google/Bing/Yahoo it.
 
nightstormer 说:
I just feel I need to comment on the 1.5x number. This used to be the standard before we had loads of ram in our computers. And if you have 2 gig ram or less you could do well with that number. I ran a 6 gig system with 3072 mb swapfile for years with no issues at all. So if you have 8 gig of ram, there is really no need for a 12 gig swapfile :smile: But a 3 gig would certainly not hurt, and we usually have room for that anyways. There are lots of documentation about this on the 'net, just Google/Bing/Yahoo it.

Good point!
(Updated initial post accordingly)

(As a side note, I have 8GB and I let Windows handle the page file, so that may also be a good solution, even though Windows usually allocates a relatively big swap file).
 
If one lets windows manage the file it tends to get a bit fragmented after a while though, and not everyone knows to defrag their drive every so often. Personally I have dedicated a small partition at the beginning of another drive and made it static, a fire-and-forget swapfile :smile: Speaking defragging, this is something people that does not know about should get used to setting up. You can greatly increase the loadtimes and game performance by regularly defragging your drive(s) if there's a lot of install/un-installs. A tad OT perhaps, but still important! :smile:
 
Treebeard 说:
Ryantheskinny 说:
After commenting out all the buffers i seem to be getting RGL errors now.  :cry:

Yes, that may be a side-effect on some systems (especially if you have a big party and are many days into the SP campaign). I haven't had them in Warband so far, but the buffer_size lines in M&B original did cause RGL errors in at least some mods (and also probably native). This means that the default engine values may fix one thing (the graphics) but cause another thing (RGL errors).

Do you have the Battle Sizer installed. If you do, try lowering the units on the battlefield to maximum 150.
Also, try lowering corpses to 0 and rag dolls to 0 and see if that helps your RGL errors.

By the way, what kind of RGL error is it?
Is it "Unable to restore Vertex Buffer"?

Edit:
Also, if you have removed your System Page File, please try putting it back to 1.5*Installed RAM.

Edit2: Updated first post to reflect this issue.

I asume thats what it was seeing as i was unable to see what it said, the game completely locked up and i had to close using taskmanager. I do have battle sizer installed so maybe that is the problem ( its set at 400) but the RGL error usally happens when the game is loading. I'll test it a little and see if anything you mentioned will help... O and I didnt try native it was a mod so maybe thats it
 
后退
顶部 底部