View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000923 | FSSCP | OpenGL | public | 2006-05-24 21:55 | 2006-05-27 10:54 |
| Reporter | Crusader | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Platform | P3 1.2Ghz, 400MBRAM, Radeon 9200 | OS | Windows | OS Version | 98SE |
| Product Version | 3.6.7 | ||||
| Summary | 0000923: OpenGL VBO greatly deforms model geometry and/or textures | ||||
| Description | Missions run normally for about 5-10 minutes. At random after that, ships abruptly deform: they stretch out, widen, become jagged and just overall make gameplay impossible. No crashes occur. | ||||
| Steps To Reproduce | Presumably this is tied directly to my Radeon 9200 / Catalyst 6.2 drivers, so reproducing it might be difficult/impossible with another video card. At any rate, i don't have to do any steps in particular to cause the bug; as long as the OpenGL VBO is *not disabled*, the ships eventually deform. | ||||
| Additional Information | Disabling the OpenGL VBO is a workaround, and i'm happy to do that for the time being. However, it would be nice to know whether i can do anything to fix the problem myself, so that the VBO can be used. Failing that, it would be nice to at least understand what causes the problem. Thanks in advance. | ||||
| Tags | No tags attached. | ||||
|
|
How much video ram is on your card? What cmdline options are you using? Is you video card (or system) overclocked? Please run a debug build and attach your fs.log file. |
|
|
Thanks for the reply. i knew i forgot something; apologies for the omitted info. --My card has 128MB of RAM --My command-line is: -spec -glow -jpgtga -mipmap -nomotiondebris -cache_bitmaps -img2dds -targetinfo -orbradar -rearm_timer -ship_choice_3d -snd_preload -nomusic -no_set_gamma -noparseerrors -novbo -window -stats -ambient_factor 85 -fov 0.50 -y_bug_fix --Neither my video card nor my system are overclocked. --i'm not currently using any enhanced textures/models. --While running the debug build and getting a logfile, i also took a screenshot of the moment when the bug occurred. The relevant point in the logfile is: Frame 8080 too long!!: frametime = 0.377 (0.377) Dumping screen to 'screen0004' Frame 8091: Weapon 0000274 CHASING cmeasure #5830 |
|
2006-05-25 06:38
|
|
|
2006-05-25 06:41
|
|
|
|
Hmm, can't find a reason for this so far. It's likely just a driver issue but I haven't found any bug reports about it. The 9200 on the Mac works fine so it's not a hardware issue and likely not a game issue. Given ATI's reputation for OpenGL driver bugs, and if no one else steps forward with this same problem, this is likely going to get closed as a driver issue. I'll try and research it some more this weekend but I don't hold much hope of an answer better than "just don't use VBOs". Sorry. |
|
|
No worries. i'm just happy that an expert had the time to take a look at it, since i was genuinely curious. Feel free to close it until/unless something useful turns up in future. And thanks again, taylor. Edit: i'd forget my head if it wasn't attached: i was going to ask, could i get a ballpark figure/back of the envelope number/wild guess/off-the-top-of-the-head estimate of any performance loss from not using the VBO? 50%? 25%? Negligible? edited on: 05-25-06 16:08 |
|
|
Performance wise, it sorta depends on the hardware/drivers. It can provide a substantial improvement in speed (as with most NVIDIA hardware and new enough drivers) or just a minor improvement. It's not a total loss though since if you can't use VBOs then it falls back on vertex arrays instead. Vertex arrays was the predecessor to VBO, and though it doesn't provide quite the speed boost that VBO will, it does help accelerate rendering. VBO basically takes that same old vertex array and stores it directly in video card RAM rather than system RAM, that's where the speed improvement comes from. Using VBOs would give you some sort of speed boost, especially with the more complex models out there, so it is preferrable to use it. But you can probably just do without it for now, wait for the next ATI driver release, and see if they fixed it or not. |
|
|
Understood. Very neat of you to humour my curiosity; i appreciate it. |
|
|
Closered. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-05-24 21:55 | Crusader | New Issue | |
| 2006-05-24 22:20 | taylor | Note Added: 0005614 | |
| 2006-05-25 06:38 | Crusader | Note Added: 0005616 | |
| 2006-05-25 06:38 | Crusader | File Added: fs.log | |
| 2006-05-25 06:41 | Crusader | File Added: screen0005.gif | |
| 2006-05-25 15:03 | taylor | Note Added: 0005620 | |
| 2006-05-25 19:57 | Crusader | Note Added: 0005623 | |
| 2006-05-25 20:08 | Crusader | Note Edited: 0005623 | |
| 2006-05-25 21:07 | taylor | Note Added: 0005624 | |
| 2006-05-26 01:35 | Crusader | Note Added: 0005627 | |
| 2006-05-27 10:54 | taylor | Status | new => closed |
| 2006-05-27 10:54 | taylor | Note Added: 0005648 |