Black Screen with 3.7.0-stable

I am having an issue where everything being rendered in the primary viewport randomly starts rendering black after a model gets attached to the rootNode.

The only exceptions are 2 alternate Viewports (for the character frames at the top left and top right) as well as the custom progress bar shader for the green, blue, red, and purple progress bars. Everything else on the guiNode and rootNode renders black:

This first happened to me 2 times in one day about 1 month ago when I was still using a 3.7 beta version, so I updated my drivers and thought that fixed it. But today it happened again with 3.7.0 stable after nearly a month of not occurring.

I had thought it was an issue with my divers juts needing updated and was hoping that had fixed it. I assumed it was because I had just installed the new call of duty black ops 6, and I thought I just messed up my drivers or something with my graphics settings as a result of installing a big bloated game on my device. I’ve had similar display issues happen to me a few years ago after I installed halo infinite and then suddenly had a ton of weird graphical bugs start happening on my pc, until I finally uninstalled it. But that was affecting stuff like the background display on my desktop, and never caused issues with my JME app like this.

So I wonder if anyone experienced anything similar with the new 3.7.0 release that could indicate that this is a jme issue? Or does this seem like it is more likely an issue with my device?

And you tried this on an older version of JME and it worked fine?

…else it might not be version specific.

Could it be related to the model?

1 Like

This is hard to answer because the issue occurs so rarely.

I could revert my game back to 3.6 but it would take at least a month without seeing the issue in order to feel confident enough to say that reverting fixed the issue, since it just took a month to happen again for only the second time.

But I would still say yes, just because I took a break from working on my game from spring until fall, and the first thing I did when coming back was upgrade to 3.7 beta.

So (conveniently) my game was in the same exact state for about a year while I was still running and testing it but not adding anything.

And then I upgraded to 3.7.0 (and I installed a big game a few days later), and then another few days later I started getting this bug for the first time.

The models are the same exact models I’ve been loading in my game for the last few JME versions, and those haven’t been changed in over a year.

The first time it happened was with a simple spell that just uses a textured JME sphere and a few particle emitters, and then 2 other times it happened with 2 different NPC models; all of which have been unchanged since as far back as jme 3.5, some even further now.

I feel like there is a good chance this is just an issue with my device that’s being triggered by any number of compounding issues since my pc is getting old and bloated: (I have a nearly full harddisk drive thats beyond due for a replacement, I recently installed some bloated aaa games that are probably beyond my device’s specs, had a dead cmos chip that I only just changed after a year of being too lazy, and probably more issues since I’ve had this PC for a while now and its becoming outdated)

But since this coincidentally began occurring after upgrading to 3.7, I figured I should still report the issue to see if anyone else has experienced anything similar.

Does it stay black? I noticed something similar when working on the shaders. In my case it was somewhat camera related, and it did not turn completely black. ( maybe indirect lighting still was applied). But i guessed i messed up something in the shader, which is still likely.

But depending on the camera movement i could always bring the lighting back.

1 Like

Yes, in this case it stays black.

I tried to cast more spells, spawn more npcs, and to move around hoping it would be reversed, but it was stuck black until I eventually closed the app.

In both cases, I was also running the most minimal scene possible that I use exclusively for testing spells or NPCs with minimal load time.

So this happened when the only thing loaded was a terrain with 1 texture, as well as my character model and a few spell and npc models that I spawned in with commands prior to the black screen happening.