GLException: GL_Invalid_value

[Disenfranchised]

So I'm having a bit of a problem here, I rarely get this error. Except for one minor inconvenience. This error happens when an enemy ship begins firing or is in the same sector as me. The game doesn't crash, but it does freeze, in which I have to CTRL-ALT-DELETE, hit cancel, and click "retry". The game then begins functioning again, until the enemy ship stops moving, or in my case is deleted. Which makes gameplay a bit difficult, and to be frank, annoying. Graphics drivers are updated to the latest drivers, and I force updated.

Log wouldn't upload, but this is the gist of the error. Failed to poll Device is written hundreds of times.

Spoiler: Log Exert

[2016-09-25 22:47:18] Failed to poll device: Failed to poll device (8007000c)

[2016-09-25 22:47:18] Failed to poll device: Failed to poll device (8007000c)

[2016-09-25 22:47:18] Failed to poll device: Failed to poll device (8007000c)

[2016-09-25 22:47:18] Failed to poll device: Failed to poll device (8007000c)

[2016-09-25 22:47:18] Failed to poll device: Failed to poll device (8007000c)

[2016-09-25 22:47:18] Exception: Projectile physics null for sector 213
[2016-09-25 22:47:18] GL_ERROR: GL_INVALID_VALUE
[2016-09-25 22:47:18] org.schema.schine.graphicsengine.core.GLException: GL_INVALID_VALUE
[2016-09-25 22:47:18] at org.schema.schine.graphicsengine.core.GlUtil.g(SourceFile:1401)
[2016-09-25 22:47:18] at obfuscated.gU.a(SourceFile:965)
[2016-09-25 22:47:18] at obfuscated.gU.e_(SourceFile:243)
[2016-09-25 22:47:18] at obfuscated.hP.e_(SourceFile:572)
[2016-09-25 22:47:18] at obfuscated.hq.e(SourceFile:531)
[2016-09-25 22:47:18] at obfuscated.hq.b(SourceFile:705)
[2016-09-25 22:47:18] at obfuscated.hq.e_(SourceFile:404)
[2016-09-25 22:47:18] at obfuscated.aAC.g(SourceFile:537)
[2016-09-25 22:47:18] at obfuscated.aAC.a(SourceFile:677)
[2016-09-25 22:47:18] at obfuscated.aAI.b(SourceFile:648)
[2016-09-25 22:47:18] at obfuscated.R.e(SourceFile:950)
[2016-09-25 22:47:18] at org.schema.game.common.Starter.startMainMenu(SourceFile:1420)
[2016-09-25 22:47:18] at org.schema.game.common.Starter.main(SourceFile:967)
[2016-09-25 22:47:18] org.schema.schine.graphicsengine.core.GLException: GL_INVALID_VALUE
[2016-09-25 22:47:18] at org.schema.schine.graphicsengine.core.GlUtil.g(SourceFile:1401)
[2016-09-25 22:47:18] at obfuscated.gU.a(SourceFile:965)
[2016-09-25 22:47:18] at obfuscated.gU.e_(SourceFile:243)
[2016-09-25 22:47:18] at obfuscated.hP.e_(SourceFile:572)
[2016-09-25 22:47:18] at obfuscated.hq.e(SourceFile:531)
[2016-09-25 22:47:18] at obfuscated.hq.b(SourceFile:705)
[2016-09-25 22:47:18] at obfuscated.hq.e_(SourceFile:404)
[2016-09-25 22:47:18] at obfuscated.aAC.g(SourceFile:537)
[2016-09-25 22:47:18] at obfuscated.aAC.a(SourceFile:677)
[2016-09-25 22:47:18] at obfuscated.aAI.b(SourceFile:648)
[2016-09-25 22:47:18] at obfuscated.R.e(SourceFile:950)
[2016-09-25 22:47:18] at org.schema.game.common.Starter.startMainMenu(SourceFile:1420)
[2016-09-25 22:47:18] at org.schema.game.common.Starter.main(SourceFile:967)
[2016-09-25 22:47:18] Exception: Projectile physics null for sector 213

 

[nightrune]

In the same folder as the logs there is graphicsinfo.txt can you upload that as well please?

 

[MrMcWalrus]

I'm having this problem as well in the same situations

 

[Jeryia]

I also see something similar intermittently. Though I get the option to 'retry', and that allows me to keep playing. Though cannon fire generally stops rendering correctly, when I do. Cannon shots are frozen in space, but I can still cause damage to ships.

It seems to happen most often when I am in build mode when under attack.

I've attached the logs from the latest instance. I see this fairly frequently, but not consistently.

graphics info:
Running on thread: main
Adapter: null
Driver Version: null
Vendor: NVIDIA Corporation
OpenGL Version: 4.5.0 NVIDIA 375.26
Renderer: GeForce GTX 780/PCIe/SSE2
GLSL Ver: 4.50 NVIDIA

System info:
OS: Fedora 25 (though I've seen this in Fedora 23 and 21)
GPU: GeForce GTX 780

 

[DrTarDIS]

I got the same error a whole bunch on a bargain-bin PC I slapped together, though with different trigger conditions. The CAUSE of the error seems to have been the C++ libraries the video driver was calling to, specifically a broken/corrupted dll. I recommend you take a look at the dependency chain of your video driver, and reinstall/update/supplement the C++ libraries it calls to.

OpenGL® Registry

 

[Jeryia]

I got the same error a whole bunch on a bargain-bin PC I slapped together, though with different trigger conditions. The CAUSE of the error seems to have been the C++ libraries the video driver was calling to, specifically a broken/corrupted dll. I recommend you take a look at the dependency chain of your video driver, and reinstall/update/supplement the C++ libraries it calls to.

OpenGL® Registry

Did a validate against all libraries required by the nvidia drivers, everything checks out as valid(including the nvidia drivers and libraries themselves). What this does is an md5sum of each of the libraries and check if it matches what's in the rpm database. So unless the rpms where built with corrupted libraries (very unlikely, as this would effect everyone who uses fedora with the nvidia drivers from rpmfusion).

I don't think this is the issue, at least on my system.

 

[DrTarDIS]

So truncation's not the issue for you, how about file version? open-source OS is a little more likely for ya to have to worry for yourself about weather the chain is up-to-date for your specific usage case. It could very well be that everyone on fedora DOES have the same problem, but they don't play starmade so never run into it...

 

[Jeryia]

Fedora is one of the bleeding edge distros. Their packages are pretty close to the latest(generally within a few months). My system itself will be up to date within 24 hours of Fedora's updates. I doubt that's it's too old.

True, It is possible that everyone on Fedora has this issue. Though, it would require that starmade be using a call in a way that is very uncommon. I run several games, and have not seen graphical issues similar to this. If this is the case I'd be happy to submit a bug to Red Hat if the call can be replicated.