WZ crash when i check my research clicking...

[wzdev-ci]

resolution_external type_bug | by cknorwid@...

---

When im clicking on the researching WZ crashed. I played on Single Player Campaign
http://img200.imageshack.us/img200/5234/17390476.jpg

---

Issue migrated from trac:937 at 2022-04-15 19:15:38 -0700

[wzdev-ci]

cknorwid@... uploaded file warzone2100.RPT (7.8 KiB)

[wzdev-ci]

cknorwid@... uploaded file warzone2100.2.RPT (7.8 KiB)

[wzdev-ci]

anonymous commented

---

dude, your drivers crashed not warzone.

[wzdev-ci]

Zarel edited the issue description

[wzdev-ci]

Zarel commented

---

It's a reproducible driver crash; we may as well fix it. Although it's a duplicate of all the other intelligence screen crash reports.

[wzdev-ci]

anonymous commented

---

Replying to Warzone2100/old-trac-import#937 (comment:3):

It's a reproducible driver crash; we may as well fix it. Although it's a duplicate of all the other intelligence screen crash reports.

you crack me up
you going to pull a bunny from your hat and fix it?
how else do you think you can fix this issue without having the source code to the drivers?

[wzdev-ci]

Zarel commented

---

Ever heard of a workaround?

[wzdev-ci]

anonymous commented

---

Sure you make it sound easy but you do not know what the issue is or have any inkling on how to fix it, right?
That is why this is highly impractical to implement a workaround for something that the people who wrote this code, I assume, can not replicate.
That is also why the OP should just use different video drivers that do not have this bug.

[wzdev-ci]

Zarel changed status from new to accepted

[wzdev-ci]

Zarel set owner to Zarel

[wzdev-ci]

Zarel commented

---

Well, assuming this is the int screen bug, it affects many known video drivers. It's possibly a violation of the OpenGL spec, which would explain why the crash is easily reproducible. It's been reported around 10 times, which means it's very common, so it shouldn't be too hard to reproduce.

Sure, it might not be very easy - it might not even be possible for me - but that's no reason not to try. Perhaps your defeatist attitude is the reason why I'm a Warzone developer and you are not.

[wzdev-ci]

anonymous commented

---

Replying to Warzone2100/old-trac-import#937 (comment:7):

Well, assuming this is the int screen bug, it affects many known video drivers. It's possibly a violation of the OpenGL spec, which would explain why the crash is easily reproducible. It's been reported around 10 times, which means it's very common, so it shouldn't be too hard to reproduce.

Sure, it might not be very easy - it might not even be possible for me - but that's no reason not to try. Perhaps your defeatist attitude is the reason why I'm a Warzone developer and you are not.

You still crack me up.
The point is, if it was a violation of the GL specs, then it would crash all drivers on all platforms. It does not. It does not matter how many times it is reported, they could all be using the same faulty driver series, and if the bug is not reported upstream, then they will never fix it.
I do not have a defeatist attitude, I have a practical attitude, and I do not suffer from the belief that everything is the fault of wz, and not a external issue.
You never know, I may just apply to be a developer...then again, with your attitude, I would end up arguing with you on almost every post / ticket. Could be fun. ;)

[wzdev-ci]

Buginator set resolution to external

[wzdev-ci]

Buginator changed status from accepted to closed

[wzdev-ci]

Buginator commented

---

I have to agree with anonymous.

We have a issue that is NOT reproducible by most of our user base. We can't reproduce this error, we can't fix it.

There is a 99% chance this is (and always will be) a video driver issue.

When I ran a openGL debugger, it came back clean, so it doesn't look like we are doing anything wrong.

Until someone has proof that it is the code at fault, and the code in question is pretty generic, then it is pretty useless to keep this open.

And it is almost impossible for us to have a workaround if we don't know what the problem is that makes those drivers choke! That is kernel level debugging...