Nordic gives black screen only
-
if this is related to the theaterdefinition file, that seems to suggest a theater switching issue. There are several ways that I know of to write theater swtiching - but the code may actually “prefer” a specific folder structure such that most things swtich properly . . . part of this is perhaps running a program like winmerge on the working vs. non-working theater on the art folder to ensure all other things being equal it genuinely is a folder structure issue and not some specific file being used that is missing something.
-
Hi, updated my previous post with more theaters tested.
Ranger keep in mind that even after restarting BMS these black screen issues are there, so its not only right after theater switching. Just to be sure we talk about the same. And yes the switching itself causes the issue but I think because the folder structure is different from the working ones.
But it could also be some graphic file format(MainUI for example) is different format, I’m not 100% sure yet which one is ultimately causing it.Also what is interesting is that some theaters give black screen MainUI right after restarting BMS like Ikaros or Iberia for example. But others have no problem with MainUI but start having black screen in Instant Action(3D), like Nordic I think it was.
Good news is that at least it could be working otherwise all theaters would have suffered this problem.
Bad news is that the fix could possibly mean theaters needed to be updated first.Cheers Obi1
-
Thanks again for this help Obi1, today I have R9 280X and win 10 and 7.
I just dl 17.7.1 (win7 and 10) and 17.12.1(win7 and 10)
now I too, can see and test this glitch (hopefully) winmerge and slowly replacing files from non working to working theaters should pin point the issue.
Please keep us posted on any progress , and I will do the same.
-
Bravo Ned, keep on track…
You will spot it.
Nikos. -
Well, I replicated the glitch in win7 with latest driver for AMD r9 280x. Win10 had no prob with the latest driver for same. So really all I accomplished so far, is verifying what Snail , Nikos, and Obi1 already told us.
The glitchy theaters have problems even before switching is complete. Ctrl,alt,del is needed to restart bms before new theater loads up the first time. Then reloading brings NTO UI , and it works fine until black lockup starting when splash screen is initiated. If you do IA mission , you can here the jet and even eject , but you will be lucky if “esc, E” gets you back to main UI.
Some quick unfinished testing so far, art folder and terrain on glitchy theaters, is not the culprit . And I set ITO directory and tdf up to mimic NTO. I need to test more today, maybe theater switching or objects folder. This is where testing seems to be pointing to right now.
Cheers
Ned -
i found it. its not different file structure. ITO will work with identical structure and tdf. i am sure it is something with objective folder. if you cancel out both objective lines and ckpit art line in NTO tdf you will see.
-
Well done Ned.
Keep us informed please.
Nikos. -
Yes good work, hope it can be solved also for other theaters with relative easy fix in the end?
In the meantime tested Battle for Balkans, this theater is ok.
Also more info on the black screens, when this is happening, also Sweetfx does not initiate. (no copyright text seen, because it actually does not start because of the black screen issue).Cheers Obi1
-
I don’t know about an easy fix for db. If I am right and this is a db issue, we may want to reach out to all 3rd party devs on Obi1’s list and try to figure out where the issue begins. I can look at these others on the list and double check that the prob lies in objects folder, but for a good db check we need a db guy that can recreate the prob himself on his sys to be able to locate and fix it.
I mean someone with win 7 and amd r9 280x. With 17.9 + driver problems.
NTO db guy is Tony and his sys has nvidia with no prob , so chances are it will be hard, or impossible for him to check this.
-
Ned,
I think it will be very difficult to replicate this . … I only have Win10 installed on my primary computer. I have a laptop with Win7 but it won’t run BMS at all . . . without having a working computer to test, I won’t be much help. Up to now I haven’t tried to rebuild the db with 3ddb tool - that might be work a try . . . I did all my work on Nordic using a combination of LODEditor, F4Browse, and BMSEditor. So, using the first two tools could have sabotaged the DB . . . perhaps using 3ddb tool can fix a few things?
-
Tested latest 17.12.2. Issue still there.
Also tested 32 bit Falcon, also got this issue.
Could it be one of the .dds files having different format?Cheers Obi1
-
Not terrain dds, I don’t know what all is in cockpit folder or objects folder, but that is where the upset is. One or both of those folders. Dds may have discrepancies there as well , but the splash and terrain dds discrepancy proved to be a non- issue with tests from Snail and me. Right now I am hoping a rebuild with 3D db builder does the trick. This may be a bigger chore then I know about, We are checking it out though.
I ran a cockpitless f16 (I turned off pits in tdf because of conflictions) with kto db through Nordic and the terrain ran fine.
The idea that dds differences between working and non working theaters is still a possibility , however the terrain tiles are not the culprit. And we have seen the discrepancy there. But it still works.
cheers -
i replaced nordic objects and cockpit art with kto and it worked fine. then i rebuilt original NTO with 3d db builder and problem still exists.
-
Hello Jan,
Any new facts since this last message? Dealing with same issue here, same vid card, win 7 .
greets,
-
No breakthrough on my end … just settled for workaround roll back of driver. I tried everything that I could with lots of help, but still didn’t find the fix. We will definitely post a big new thread if problem gets solved.
-
Also here, no news, have tried mixing ati driver dlls from working with non working, but I stopped with experimenting with it after 10 installs.
Just not sure what part of the driver has introduced the issue.
Every now and then I try a newer update, but revert back when its still broken.Cheers Obi1