Jump to content
The simFlight Network Forums

Recommended Posts

Posted

I know there are some post on black screens but I haven't found my specific problem.

After displaying Text from my programme in FS2004 I get black screens if I switch the view (e.g. from VC to 2d cockpit).

The same routine of displaying the text in FS2002 was working fine. Any hinds on what I have to take care for especially in FS2004?

Posted

After displaying Text from my programme in FS2004 I get black screens if I switch the view (e.g. from VC to 2d cockpit).

I don't know of any reasons for that, but most all the black screen phenomena were with switching modes, like VC/2D, Minimise/Restore, Looking left/right, et cetera, and I think, by comparison with the same sorts of things hapening in many other DX8/DX9 games it was narrowed down to video driver progblems. Most eventuially got resolved by video updates, though it was a difficult time.

I'm not sure what you mean by "displaying Text from my programme in FS2004". Is this the facility in FSUIPC? What happens if you divert it using AdvDisplay?

Regards,

Pete

Posted

Well... I am on the newest available Video Driver.

I have no problems with switching views an black screens before.

What I do is to use FSUIPC, entering my zero determined text into &H3380

and put &HFFFD into &H32FA.

The text is displayed but after that I cannot switch to a different screen anymore because of the black-screen effect. Again, without this action I have no black screen effect at all.

I just wonder if someone has discover this problem, too.

I know that FSUIPC didn't do anything in manipulating graphic related stuff. But fact is, after setting the text the problem is there, before not.

I can try with AdvDisplay, just to see what happens.

Posted

Shit... same things happening.

After sending the text it get's displayed and after that any change of the view leads to the black screen. :-(

By the way, displaying text from a MS Adventure is working without any problem.

Well... if I can find a solution (or wait until there is a Nvida driver without producing this bs :roll: ) I will tell.

Posted

What I do is to use FSUIPC, entering my zero determined text into &H3380

and put &HFFFD into &H32FA.

Is the problem the same with non-scrolling test, or with a different delay specified? The fact that the same thing happens when you have AdvDisplay intercepting the request instead is strange -- the action is completely different then.

Can you turn on FSUIPC IPC write logging and show me the extract, showing what you are doing? Maybe there's some obscure problem resulting in some corruption somewhere.

Regards,

Pete

Posted

Hi Pete,

yes, same happens with non-scrolling text.

Sadly I cannot attache here something.

I send the logfile to you.

I will have also some tests on the computers of my collegues so I can figure out if it's just on my PC.

Posted

yes, same happens with non-scrolling text.

Hmmmthere are a lot of programs using those facilities without any problems. I need to see the logging to see if there's anything out of the ordinary.

Sadly I cannot attache here something.

I send the logfile to you.

Ahare you Michael Garbers? If so, it has just arrived -- I'll look at it now.

[later]

Hmmm. It would have been a much smaller log if you had only enabled IPC write logging -- we don't need to look at reads.

Anyway, I think you have made a rather nasty mistake. See this:

119592 WRITE0 3380, 128 bytes: 48 41 4D 42 55 52 47 20 44 20 32 30 35 33 20 41

...

119592 WRITE0 3400, 32 bytes: 00 00 00 00 00 00 00 00 00 00 00 00

...

119592 WRITE0 3420, 8 bytes: 00 00 00 00 00 00 00 00

119592 WRITE0 3428, 16 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

119592 WRITE0 3438, 32 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

...

119592 WRITE0 3458, 79 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

...

You appear not only to be writing to the 128 byte message area at 3380, but also another 168 bytes, right up to offset 34A7 -- a total of 296 bytes!!! (You may be doing this in one "FSUIPC_Write" -- the reason they are logged like this is that each of the offsets you see listed is mapped internally to a different place within FS).

Some of the offsets in the 34xx range are known and documented in the second table in the programmers guide, but the others could do anything in FS, and probably different things in different versions. you should never write to unknown offsets or write to offsets which are known but which you don't want to change.

Your write to 32FA seems odd too:

119592 WRITE0 32FA, 2 bytes: 00 03

The value 0300 is 768 in decimal, saying "display this for 768 seconds". Are you sure that's what you want?

Regards,

Pete

Posted

Yes I am Michael,

thank you for looking at this. Always good if a second person can have a look at. And you are right....

You know what fools me? In the SDK you put the address offset in Hex and the size in decimal. That's why I was going wrong. Shame on me.

The second one

-------------------------------------------

Your write to 32FA seems odd too:

119592 WRITE0 32FA, 2 bytes: 00 03

-------------------------------------------

was just for testing. :-)

Posted

You know what fools me? In the SDK you put the address offset in Hex and the size in decimal. That's why I was going wrong.

Ah, sorry about thatit's always been that way though. At least you won't make that mistake again! :)

Regards,

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.