Screen goes black when changing some parts

[Eskimo1313]

When changing any experimental effect on a module or sometimes when changing out a module the screen will go black and nothing is clickable and the page needs to be refreshed.

[alex-williams]

I haven't been able to replicate this issue, so I'll need more information to be able to do so. If this happens again, please tell me exactly what you were doing when it happened. The ship, the module, the engineering blueprint and the experimental effect and ideally, the link to the build and I will try to reproduce the problem you're seeing.

[Eskimo1313]

https://sh.orbis.zone/oeugK2QdTp here is one ship that it is happening to but it seems to happen on any of my saved builds or starting a new one. Clicking on the wrench on an already engineered part and then moving the mouse down to the experimental effect makes the screen go black. On a new build with no engineering once I click on the grade of a part that can have an experimental the screen goes black. On life support which has no experimental options I am able to apply the engineering level and the screen is fine. Trying this in an incognito window also caused this and I also tried on Brave and Chrome and happens on both

(the second mouse was from just recording the gif)

[alex-williams]

Thank you for the response and especially the GIF, as this allows me to see it happening. Unfortunately, I still cannot reproduce the problem, even using the build you've linked and trying to do the exact same stuff you've done in the GIF. This leads me to believe it must be an issue on your computer, somehow... the app is run by the browser, not by the web server, so this isn't particularly unusual, however usually there's an identifiable problem in the app, causing the problem.

Whatever it is, seems to be a problem on your computer itself, not in the browser, as you've said you've used incognito and Brave, as well as Chrome. Can you open the developer tools in Chrome before triggering this and ensure that the developer tools panel is focused on the 'console' tab, then trigger this again, but make the video a little clearer so that I can read what the output in the console is? This might give us a clue, as to what is causing the problem. Also, while you're at it, any extensions you may have installed in both browsers, that affect Javascript (Ad Blockers for example, manipulate and block Javascript from running) should be turned off, to rule out the possibility that they're crashing the app.

[Eskimo1313]

error 185 is what pops up when the screen goes black

[alex-williams]

If you look in the bottom right hand corner of the screen, you should see the current Coriolis version number, can you let me know what it is please? Also, can you try a 'Ctrl + Shift + R' and see if the error still occurs? It's almost like you're running an older version of the app in your browser cache. Although, I don't know if you previously ran the app in Brave before testing to reproduce the error... but it's still worth a try, as no one else seems to be experiencing the issue and I can't reproduce it. I've even had an AI Coding assistant assess the code to find anything that might cause the error and so far, I'm coming up empty. It's creating an infinite loop when you're trying to add an experimental effect, but it shouldn't be.

[Eskimo1313]

4.0.17 - 2026-05-03 is what is on the bottom right of the screen. cntrl shift r didn't help and I also tried clearing the cache on chrome.
Here is a pic of the issues tab

[alex-williams]

The issues tab, is just giving HTML compliance violations. Every element should have an ID, but that isn't causing your error. Do you have any extensions installed in Chrome? Specifically, extensions you have in both Chrome and Brave? The app itself, seems to be clean and no one else is reporting the issue, so I can only think that something on your machine is interacting with react and causing the error. Any extensions that mess around with HTML, Javascript, or things like React Dev Tools, for example, might try to intervene in how the app is running and cause this kind of an issue.

[Eskimo1313]

I used brave to test uninstalling all my extensions and it still happens on brave with no extensions left

[alex-williams]

Ok, I've introduced an error boundary, so that hopefully the app reports errors a little better and we might have more information. I've only deployed it to the alpha site though, so if you could use this link https://sh.orbis.zone/4xsKe0c55I and try to reproduce the error again on the alpha site, then let me know what you get back in terms of errors.

[Eskimo1313]

still does the same on chrome and brave. Tried to turn off hardware accel on brave with no change

[alex-williams]

hmmm, have you tried the 'clear current build and reload' button?

[Eskimo1313]

yea I tried both although clear current build keeps the engineering and modules still

[Eskimo1313]

yellow warning is new

[Eskimo1313]

switching the stat box to classic view makes it happen almost as soon as I mouse over the stats. I moved the mouse slow over the stats to see exactly where it happened but it happens no matter how fast I move over it

20260504-1322-17.8448024.mp4