An Missile/Cannon weapon controlled by a Delay <> NOT clock throws GL_INVALID_VALUE very often, game can still resume after.
Description
Description
Details
Details
- Task Type
- Bug
Testing Results
- Affected Gamemode(s)
- Singleplayer
- Reproducible
- Yes
- Last tested (version)
- 0.199.535
- Category
- Control Block System: Weapons
- First occurrence (version)
- 0.199.353
Hardware/Software/System
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
Steps to reproduce
- Spawn a core, build a Missile/Cannon weapon and connect it to a Delay <> NOT clock
- Activate the clock and wait
- GL_INVALID_VALUE will be thrown periodically
Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>
Related Objects
Related Objects
Event Timeline
Comment Actions
logstarmade (snipped due to excessive repetition of Exception: Projectile physics null for sector x
Comment Actions
-Feedback-
I can't reproduce but seems to be something related to missiles indeed. Were you using a specific ship to reproduce this? I tried out some missile + cannon ones but I'm not triggering it.
Could depend on the amount of missiles, on sector size and where you shoot, on missile range, on speed, ...
Comment Actions
I can't remember anything related to this task to be fixed in the latest release although some shaders did change, perhaps that did fix something. I'll keep the task open for a while so if you find some clue what you need more to get to reproduce this, make sure to leave a message here.
Comment Actions
Hmm could be,
I have not seen this on my laptop (which uses the intel's built in graphics). I checked all the logfiles I have saved and came up with nothing, though I don't use it much in starmade. Laptop also Runs Fedora 25.
The main system uses the nvidia drivers (from nvidia) taht I have seen this issue on.
Comment Actions
The set-up explained in the original description does not replicate it anymore, however I still do get the error but it is very hard to reproduce it reliably (however when using a missile system that causes it, it happens very reliably), I have only experienced it twice since then, both in multiplayer. I am using a Nvidia card as well. However, another SM player has this issue on AMD cards as well.
Comment Actions
-rejected-
Unfortunately without a way to reproduce it consistently, it's not possible to find out if it's something related to drivers or with starmade.
You could brute force this issues to happen by holding F1 and F2, but I'm still unable to trigger anything related to it involving missiles or explosions.