Yes, essentially you have two options ahead of you:
- create a minimal test case (one class preferably) that illustrates the problem so that others might test it on their GPU setups and comment appropriately (or maybe we’ll just spot the problem)
- or build JME from source starting with the 3.2.0 tag and walking forward a commit at a time until it breaks. I’ve done this before… it’s not ‘fun’ but it can be satisfying to find the specific commit.
…in the end it could still turn out to be system-specific, though. So a test-case is not a bad idea.
Also, in your testing I hope you were able to repeat the results several times in a row… else you might fall into the “backwards clock” trap. Short version of the story:
My dad tells a story about a broken electric wall clock that they took apart to try and fix. When they put it back together it ran backwards. So they unplugged it to look again… when they plugged it back in it ran fine. Turns out unplugging it and plugging it back in caused it to switch directions. Forward, unplug, plug back in, backward, unplug, plug back in, forward…
In the U.S., a standard ungrounded wall plug can be flipped and work just fine. My dad and his co-workers had their boss thinking he was crazy as they tried to convince him that flipping the “polarity” caused the clock to run in a different direction.
Plugged in: clock runs forward
Unplug, flip the plug over, plug it back in: clock runs backwards
Had their boss questioning everything he knew about alternating current.
Lesson: be careful your variables and assumptions. Something is only failing if it fails three or four times in a row under the same conditions.