FSUIPC v3.06 3.07 3.08 and blackscreen

[pastaga]

Objet : Black Screen between Full screen and windowed with FS2004/FS2002

Intel 2.Ghz FX 5600 ultra Ram 768

Bonjour,

I have installed the Fsuipc v3.07 and was very interested in the "black screen bug" correction as explained in the documentation.(I had this bug with V 3.06)

Unhappily,setting InitDelay=0 or InitDelay=3000 in the Fsuipc.ini does'nt solve the pb. I use S-Combo and the pb appears in the following conditions:

Running FS9 and beeing at a gate of an airport in full screen.

Desactiving full screen in order to put "on" S-Combo.

FS9 is now "windowed". Connect S-Combo to FS

Reactiving full screen in the top bar of the windowed FS9

At this point I obtain a black screen and if I try to solve that, FS9 hangs.

The only way I founded not to have black screen is this one:

Running FS9 and being at a gate of an airport

Push Alt Esc to put FS9 in the task bar

Connect S-Combo

Click on the FS task bar to come back in full screen.

With this new set of operations,all works well,no more blackscreen or hang of FS9

The pb appears ONLY when I try to go back from windowed screen in full screen. Is this kind of bug you addressed with FSuipc 3.07 ?

PS.

I've just installed v 3.08 and the problem is always there.

Good News : v3.08 works well with FS2002

Bad News : Always the pb with FS9

Too bad!

Thanks for your help.

[Pete Dowson]

I've just installed v 3.08 and the problem is always there.

Yes, as I said many times, the bug is not in FSUIPC, but either in FS or, more likely, looking at all the other games and programs which suffer in the same way, DX9. I hope Microsoft will be able to fix it.

All I found was, on my system and on many others, changing the timing of FSUIPC (and also AdvDisplay and PFC.DLL) helped. There's also ViMaCore2004.DLL which did it on my system (I don't know about others), and there may be others.

Alternative video drivers also help, sometimes, with some systems. But I think all these little things do is subtly alter the timing here and there. it is almost certainly some clash between some call and an interrupt, or similar.

But, sorry, until Microsoft deal with this (I suspect it will have to be by a DX revision) there is no single answer. All I tried to do was help a bit -- sorry it didn't work for you, but I'm glad you found a work-around that you can use.

Regards,

Pete

[pastaga]

Thank you Pete for your quick answer.

I would want an explanation concerning the following paragraph from FSuipc user guide.You writed:

"In the end the only change that made any different was setting “InitDelay=0” in FSUIPC.INI. This makes FSUIPC subclass the main FS window directly it is loaded, instead of delaying it. With that change it was well nigh impossible for me to cause the black screen problem.

As a consequence of this I now default this parameter (since version 3.07), and I also changed AdvDisplay.DLL and PFC.DLL to subclass early too."

I understood that from the 3.07 version you had added a line "InitDelay=0 in the Fsuipc.ini

May be i don't well understand this point but i have not seen such a line in the Fsuipc.ini

So i've done a try.I have put myself this line in the Fsuipc.ini

No changes with FS9.The pb is still there.

I have looked at the fsuipc.ini after my try and i was surprised not to see the line i had put in the ini file.It seems that the ini file is rewrited by FSUIPC after each operation?

Can you explain that to me?

Many thanks in advance

[Pete Dowson]

I understood that from the 3.07 version you had added a line "InitDelay=0 in the Fsuipc.ini

No, as I say in the text, I defaulted the value of InitDelay to 0, instead of 3000 as in previous versions. If the parameter is omitted, which it is usually, then the default value is used.

I have looked at the fsuipc.ini after my try and i was surprised not to see the line i had put in the ini file.It seems that the ini file is rewrited by FSUIPC after each operation?

If the value of InitDelay is the default value then it isn't needed in FSUIPC.INI and is removed. You will only see it, and it is only needed, if you want it to be something other than the default.

BTW I here reproduce the text from another user (Jonathan Clay) who did some research on Microsoft's database about black screen problems. You might be surprised at how universal they are with DX9. This is from another thread but it is getting lost deep in this Forum, so it will be useful to reprise it:

I found these by searching for the exact phrase "black screen" on the MS knowledgebase. I also did another search "flight black screen" where I asked for a match on all words. Some good ones:

Games: The Screen Turns Black

http://support.microsoft.com/default.as-us;813712

Black Screen When You Run a DirectX-Based Program

http://support.microsoft.com/default.as-us;184541

Games: How to Troubleshoot Display Issues

http://support.microsoft.com/default.as-us;263039

Games: Hangs or Slow Performance on AMD System with VIA Chipset

http://support.microsoft.com/default.as-us;274629

Regards,

Pete