Jump to content
The simFlight Network Forums

Recommended Posts

Hi Paul,
I have an issue with catching one specific GSX menue item. Basically my GSX remote control works very reliable and I can catch all menue items and messages.

Only with one single message I have an issue, which seems to be a timing problem or overlap with an other GSX message.

MenuTitleText: GSX - Pushback Service
MenuPromptText: Do you want to request Pushback?  (Appears if pushback direction is set to 'None' for a specific position)

The message is mixed with some other menue data. Start at 0xB03D, End 0xB051

[GSX] Handling by LOSCH Airport Service appears at the green banner contemporaneous with the message 'Do you want to request Pushback?' (Might be part of the problem)

3461531  READ0[33552]  B000,  2048 bytes: FA B7 37 00 01 01 00 00 00 00 C0 40 00 00 00 00  ..7........@....
  3461531                           28 00 00 00 5B 47 53 58 5D 20 48 61 6E 64 6C 69  (...[GSX] Handli
  3461531                           6E 67 20 62 79 20 4C 4F 53 43 48 20 41 69 72 70  ng by LOSCH Airp
  3461531                           6F 72 74 20 53 65 72 76 69 63 65 00 00 75 65 73  ort Service..ues
  3461531                           74 20 50 75 73 68 62 61 63 6B 3F 00 59 65 73 00  t Pushback?.Yes.
  3461531                           4E 6F 00 00 68 61 6E 73 61 00 41 65 72 6F 67 61  No..hansa.Aeroga
  3461531                           74 65 00 45 46 4D 20 2D 20 47 65 73 65 6C 6C 73  te.EFM - Gesells
  3461531                           63 68 61 66 74 20 66 75 72 20 45 6E 74 65 69 73  chaft fur Enteis
  3461531                           65 6E 20 26 20 46 6C 75 67 7A 65 75 67 73 63 68  en & Flugzeugsch
  3461531                           6C 65 70 70 65 6E 20 4D 75 6E 63 68 65 6E 00 4C  leppen Munchen.L
  3461531                           4F 53 43 48 20 41 69 72 70 6F 72 74 20 53 65 72  OSCH Airport Ser
  3461531                           76 69 63 65 20 20 5B 47 53 58 20 64 65 66 61 75  vice  [GSX defau
  3461531                           6C 74 20 63 68 6F 69 63 65 5D 00 00 72 65 00 4F  lt choice]..re.O
  3461531                           70 65 72 61 74 65 20 73 74 61 69 72 73 00 43 75  perate stairs.Cu
  3461531                           73 74 6F 6D 69 7A 65 20 74 68 69 73 20 70 61 72  stomize this par
  3461531                           6B 69 6E 67 20 70 6F 73 69 74 69 6F 6E 00 52 65  king position.Re
  3461531                           70 6F 73 69 74 69 6F 6E 20 61 69 72 63 72 61 66  position aircraf
  3461531                           74 00 00 6D 20 72 65 66 75 65 6C 69 6E 67 20 75  t..m refueling u
  3461531                           73 69 6E 67 20 64 65 66 61 75 6C 74 20 46 75 65  sing default Fue
  3461531                           6C 20 6D 65 6E 75 00 00 00 00 00 00 00 00 00 00  l menu..........

The previous 2048 byte structure was empty. So I can not explain were the rest of the data comes from. This menue items have been displayed some menues before.

3460875  READ0[33552]  B000,  2048 bytes: 6C B2 37 00 00 02 00 00 00 00 00 00 00 00 00 00  l.7.............
  3460875                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  3460875                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Would be great to get some help.

Ruediger

 

Link to post
Share on other sites

Looking at the data:

  3461531  READ0[33552]  B000,  2048 bytes: FA B7 37 00 01 01 00 00 00 00 C0 40 00 00 00 00  ..7........@....
  3461531                           28 00 00 00 5B 47 53 58 5D 20 48 61 6E 64 6C 69  (...[GSX] Handli
  3461531                           6E 67 20 62 79 20 4C 4F 53 43 48 20 41 69 72 70  ng by LOSCH Airp
  3461531                           6F 72 74 20 53 65 72 76 69 63 65 00 00

the length of the supplied data stated is 0028 (40 bytes). This is not a menu -- it is type 0x0101 which is a non-scrolling text line, and it terminates with the 00 00.

Pete

 

 

Link to post
Share on other sites

Ok, I understand. Then the problem is one step before:

3460875  READ0[33552]  B000,  2048 bytes: 6C B2 37 00 00 02 00 00 00 00 00 00 00 00 00 00  l.7.............
  3460875                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  3460875                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Then the previous should contain the menu. But the structure is empty.

The sequnce is:

3459421  READ0[33552]  B000,  2048 bytes: 51 9F 37 00 00 02 00 00 00 00 20 41 00 00 00 00  Q.7....... A....
  3459421                           B7 00 00 00 53 65 6C 65 63 74 20 6F 70 65 72 61  ....Select opera
  3459421                           74 6F 72 20 61 74 20 47 61 74 65 20 33 34 35 00  tor at Gate 345.
  3459421                           53 65 6C 65 63 74 20 68 61 6E 64 6C 69 6E 67 20  Select handling
  3459421                           6F 70 65 72 61 74 6F 72 00 43 6F 6E 64 6F 72 00  operator.Condor.
  3459421                           4C 75 66 74 68 61 6E 73 61 00 41 65 72 6F 67 61  Lufthansa.Aeroga
  3459421                           74 65 00 45 46 4D 20 2D 20 47 65 73 65 6C 6C 73  te.EFM - Gesells
  3459421                           63 68 61 66 74 20 66 75 72 20 45 6E 74 65 69 73  chaft fur Enteis
  3459421                           65 6E 20 26 20 46 6C 75 67 7A 65 75 67 73 63 68  en & Flugzeugsch
  3459421                           6C 65 70 70 65 6E 20 4D 75 6E 63 68 65 6E 00 4C  leppen Munchen.L
  3459421                           4F 53 43 48 20 41 69 72 70 6F 72 74 20 53 65 72  OSCH Airport Ser
  3459421                           76 69 63 65 20 20 5B 47 53 58 20 64 65 66 61 75  vice  [GSX defau
  3459421                           6C 74 20 63 68 6F 69 63 65 5D 00 00 72 65 00 4F  lt choice]..re.O
  3459421                           70 65 72 61 74 65 20 73 74 61 69 72 73 00 43 75  perate stairs.Cu
  3459421                           73 74 6F 6D 69 7A 65 20 74 68 69 73 20 70 61 72  stomize this par
  3459421                           6B 69 6E 67 20 70 6F 73 69 74 69 6F 6E 00 52 65  king position.Re
  3459421                           70 6F 73 69 74 69 6F 6E 20 61 69 72 63 72 61 66  position aircraf
  3459421                           74 00 00 6D 20 72 65 66 75 65 6C 69 6E 67 20 75  t..m refueling u
  3459421                           73 69 6E 67 20 64 65 66 61 75 6C 74 20 46 75 65  sing default Fue
  3459421                           6C 20 6D 65 6E 75 00 00 00 00 00 00 00 00 00 00  l menu..........

The above is ok and captured.

The next one should contain the menu:

MenuTitleText: GSX - Pushback Service
MenuPromptText: Do you want to request Pushback?

Nothing captured, it's empty:

3460875  READ0[33552]  B000,  2048 bytes: 6C B2 37 00 00 02 00 00 00 00 00 00 00 00 00 00  l.7.............
  3460875                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  3460875                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

This on is followed by:

3461531  READ0[33552]  B000,  2048 bytes: FA B7 37 00 01 01 00 00 00 00 C0 40 00 00 00 00  ..7........@....
  3461531                           28 00 00 00 5B 47 53 58 5D 20 48 61 6E 64 6C 69  (...[GSX] Handli
  3461531                           6E 67 20 62 79 20 4C 4F 53 43 48 20 41 69 72 70  ng by LOSCH Airp
  3461531                           6F 72 74 20 53 65 72 76 69 63 65 00 00 75 65 73  ort Service..ues
  3461531                           74 20 50 75 73 68 62 61 63 6B 3F 00 59 65 73 00  t Pushback?.Yes.
  3461531                           4E 6F 00 00 68 61 6E 73 61 00 41 65 72 6F 67 61  No..

This capure contains the message ([GSX] Handling by LOSCH Airport Service) and part of the menue expected in 3460875 'ues t Pushback?.Yes.No'.  Which is recognized as Menu (0002), but not captured at this point in time.

Ruediger

 

Link to post
Share on other sites

Can you please try it with a Lua plug-in, so I can see what is going on sequentially. It is not easy to understand when I don't know your program.

The facility was designed for use in Lua plug-ins, via the event.textmenu function.  The dumping into the offsets for program use instead was an after thought, but for clarity here I'd like you to check results with a plug-in, please.

I'm not sure you are in the right place, by the way. If this is really a question of some special textmenu support in Paul's DLL (this is his forum) then I think he will need to intervene. But let us check that the original method works.

Pete

 

Link to post
Share on other sites

Hi Pete,
I did some tests with a LUA script and event.textmenu. My LUA test scenario writes all appearing menus and messages in a text file, so I can easily review them. The result is the same as with the fsuipcclient.dll. All menus are captured except the one mentioned in my previous post.

********* LUA: "CatchGSXMenu2" Log [from FSUIPC version 6.0.11] *********
  7672046 LUA: text and menu function type 2 messages 11 >>>> GSX Ground Service menue
  7676687 LUA: text and menu function type 1 messages 1 >> Depature Cearing Request (green banner)
  7677109 LUA: text and menu function type 2 messages 7 >>>> Handling Operator menue
  7687453 LUA: text and menu function type 1 messages 1 >>>> Handling by LOSCH Airport Service (green banner)

Now the suprise. I did the test about ten times. In one test run the missing menue was capured:

 7964140 LUA: text and menu function type 2 messages 11
  7966765 LUA: text and menu function type 2 messages 7
  7968531 LUA: text and menu function type 2 messages 4 !!!!!!
  7969484 LUA: text and menu function type 1 messages 1
  7975468 LUA: text and menu function type 1 messages 1
 

Ruediger

 

Link to post
Share on other sites
18 hours ago, Delphi said:

I did some tests with a LUA script and event.textmenu. My LUA test scenario writes all appearing menus and messages in a text file, so I can easily review them. The result is the same as with the fsuipcclient.dll. All menus are captured except the one mentioned in my previous post.

So those two are appearing faster than the results can be processed correctly. I don't think there's much we can do about that as the interception is a blanket facility -- you get them all or none. It would be possible is to separate the types into different offsets, but that would have ramifications for existing applications, including the WideClient access from client PCs (which is where the facilities were first implemented, and the main reason for them -- to get the messages and menus onto a separate screen, probably inside a cockpit.

Just to check the timings so I can fully understand this, could you run the test again, but first add

Debug=Please
TestOptions=x8000

to the [General] section of the INI file.

This will log the reception of the text as soon as it is signalled to FSUIPC, and I can see then the milliseconds difference. Maybe a workable solution would be to buffer the arrival of text arriving in less than so many mSecs after a previous one, keeping it separate for a defined period (adjustable or fixed? Don't know) before placing it into the same offsets. That period would need to be enough for other processes, including WideFS, to extract the data from the offsets.

It is a little strange that I've used GSX2 with WideClient doing the displays for me (suppressed on the P3D screen) and not noticed such a problem before, but I must admit I've not tried it for quite a while now. Too much other stuff to attend to.

BTW this thread definitely should be in the main FSUIPC Support Forum. I'll move it after your next reply.

Pete

P.S.  If you didn't need to process the text message which is overwriting the menu, then you could try using a Message Filter as an interim solution. Assuming, that is, the message is always the same and that there are no others you actually want also starting with the same first 16 characters. (See the section "Message Filters" near the back of the FSUIPC Advanced Guide).

 

 

Link to post
Share on other sites

Hi Pete,
as requested:

>>>>FSUIPC6.log

[GSX] A simulator update has been applied, please run GSX Level 2 Control Panel, and click the Disable Default Jetways button.
   323687 ***DISP*** Text/menu type 1 broadcast
   329500 ### TEXT_DESTROY: 258 (Static) Result: 65540, Flags 00000000
   329500 ***DISP*** Text/menu type 1 clear broadcast
   331625 ### TEXT: 512 (Menu) From SimC, Duration 30.00, Flags 00000000, Len=254
   331625      GSX - Activate ground services
   331625      Activate ground services
   331625      Request deboarding
   331625      Request catering service
   331625      Request refueling
   331625      Request boarding
   331625      Prepare for push-back and departure
   331625      No jetways here
   331625      Operate stairs
   331625      Customize this parking position
   331625      Reposition aircraft
   331625 ***DISP*** Text/menu type 2 broadcast
   337703 ### TEXT_DESTROY: 512 (Menu) Result: 4, Flags 00000000
   337703 ***DISP*** Text/menu type 2 clear broadcast
   337750 ### TEXT: 257 (Static) From SimC, Duration 6.00, Flags 00000000, Len=36
   337750
[GSX] Departure clearance requested
   337750 ***DISP*** Text/menu type 1 broadcast
   337984 ### TEXT: 512 (Menu) From SimC, Duration 10.00, Flags 00000000, Len=183
   337984      Select operator at Gate 345
   337984      Select handling operator
   337984      Condor
   337984      Lufthansa  [GSX default choice]
   337984      Aerogate
   337984      EFM - Gesellschaft fur Enteisen & Flugzeugschleppen Munchen
   337984      LOSCH Airport Service
   337984 ***DISP*** Text/menu type 2 broadcast
   342453 ### TEXT_DESTROY: 512 (Menu) Result: 4, Flags 00000000
   342453 ***DISP*** Text/menu type 2 clear broadcast
   343921 ### TEXT_DESTROY: 257 (Static) Result: 65540, Flags 00000000
   343921 ***DISP*** Text/menu type 1 clear broadcast
   345375 ### TEXT: 512 (Menu) From SimC, Duration 30.00, Flags 00000000, Len=63
   345375      GSX - Pushback Service
   345375      Do you want to request Pushback?
   345375      Yes
   345375      No
   345390 ***DISP*** Text/menu type 2 broadcast
   345390 ### TEXT: 257 (Static) From SimC, Duration 6.00, Flags 00000000, Len=40
   345390
[GSX] Handling by LOSCH Airport Service
   345390 ***DISP*** Text/menu type 1 broadcast
   351375 ### TEXT_DESTROY: 257 (Static) Result: 65540, Flags 00000000
   351375 ***DISP*** Text/menu type 1 clear broadcast
   375406 ### TEXT_DESTROY: 512 (Menu) Result: 65540, Flags 00000000
   375406 ***DISP*** Text/menu type 2 clear broadcast
   375781 ### TEXT: 257 (Static) From SimC, Duration 6.00, Flags 00000000, Len=23
   375781
[GSX] Have a good trip
   375781 ***DISP*** Text/menu type 1 broadcast
   381781 ### TEXT_DESTROY: 257 (Static) Result: 65540, Flags 00000000
   381781 ***DISP*** Text/menu type 1 clear broadcast

**************************************************************************************
>>>>>LUA log (belonging to the sequence as shown in the FSUIPC6.log (Menue Do you want to request Pushback? (345375) missing.

********* LUA: "CatchGSXMenu2" Log [from FSUIPC version 6.0.11] *********
   291062 System time = 24/02/2021 17:22:13, Simulator time = 12:00:17 (10:00Z)
   291062 LUA: beginning "C:\Users\ruedi\Documents\Prepar3D v5 Add-ons\FSUIPC6\CatchGSXMenu2.lua"
   293093 LUA: text and menu function type 1 messages 1
   323703 LUA: text and menu function type 1 messages 1
   331625 LUA: text and menu function type 2 messages 11
   337750 LUA: text and menu function type 1 messages 1
   337984 LUA: text and menu function type 2 messages 7
   345390 LUA: text and menu function type 1 messages 1
   375781 LUA: text and menu function type 1 messages 1

**************************************************************************************
I did the test run 10 times. In 2 of the runs the menue was captured.

I did additional test runs with:

[MessageFilters]
Suppress="[GSX] Handling"

In all 10 runs the menue was captured. However, I'm not sure whether I understand the function of the messagefilter right. I was expecting that the message gets suppressed and is not shown at the green banner. But it did.

Ruediger

Link to post
Share on other sites

Thanks. Very interesting. The previous menu:

13 hours ago, Delphi said:

   337984 ### TEXT: 512 (Menu) From SimC, Duration 10.00, Flags 00000000, Len=183
   337984      Select operator at Gate 345
   337984      Select handling operator
   337984      Condor
   337984      Lufthansa  [GSX default choice]
   337984      Aerogate
   337984      EFM - Gesellschaft fur Enteisen & Flugzeugschleppen Munchen
   337984      LOSCH Airport Service
   337984 ***DISP*** Text/menu type 2 broadcast

was dispatched immediately (the "broadcast" message is when the offsets are updated), but the problem one:

13 hours ago, Delphi said:

   345375 ### TEXT: 512 (Menu) From SimC, Duration 30.00, Flags 00000000, Len=63
   345375      GSX - Pushback Service
   345375      Do you want to request Pushback?
   345375      Yes
   345375      No
   345390 ***DISP*** Text/menu type 2 broadcast

appears to have been delayed by 15 mSec --  enough for the following text message to overwrite it:

13 hours ago, Delphi said:

   345390 ### TEXT: 257 (Static) From SimC, Duration 6.00, Flags 00000000, Len=40
   345390
[GSX] Handling by LOSCH Airport Service
   345390 ***DISP*** Text/menu type 1 broadcast

I think the arrival of the new message so quickly after the menu somehow interrupts the flow of the menu processing in FSUIPC.

I think the only answer is to artificially delay the "broadcast" of any message X millisecs after one of a different type is broadcast. (It doesn't matter if the types are the same, because the latter should overwrite the former as it would on screen).

The question then is how long to keep them pending (X=?).  I could make it adjustable but I need a default. Maybe start with 100 mSecs and experiment with lower? If I send you a test version you could run your tests again and let me know the minimum delay which works for you, then for the default I'd just add a bit in case of PC and user application variation. Okay?

By the way, if you de-select the Logging option to log lua plug-ins separately, the log entries for the plug-in would appear in their proper position in the main log, instead of trying to match them up afterwards.

14 hours ago, Delphi said:

However, I'm not sure whether I understand the function of the messagefilter right. I was expecting that the message gets suppressed and is not shown at the green banner. But it did.

With P3D message displays can only be suppressed on the P3D screen by using the Text display option in the P3D UI. The FSUIPC filtering just operates on the feeding of the text to the Lua plug-ins and offsets. The messages are checked and discarded -- instead of being buffered and delayed as proposed above.

I'm moving this thread now ...

Pete

 

  • Like 1
Link to post
Share on other sites
On 2/25/2021 at 9:33 AM, Delphi said:

many thanks for your investigations. Yes, please send me the test version.

Please install the attached version (6.0.13a) in your FSUIPC6 installation folder, overwriting the version already there.

Let me know the results, please. If still not good, I'll need the same information as before. Here I've tested as well as I can without actually having the same problems as yourself -- I've had to try to simulate them.

There's a new parameter in the [General] section of the FSUIPC6.INI file:

TimeToDelayTexts=100

This simply says to delay the posting of changes to either the offsets or to event.textmenu for 100 mSecs after a posting of a different type of message (i.e menu vs message vs display window text). For posts of the same type they are allowed to overwrite as they would do on screen.

100 mSecs seems reasonable to me, but you can try increasing or decreasing it to see what happens. I'd like to know about this before deciding on the final default value (assuming, of course, that the logic actually works for you with some value).

Pete

FSUIPC6.dll

 

Link to post
Share on other sites
4 minutes ago, Pete Dowson said:

Why, has it affected your applications too? I've had no feedback from your good self on this.

Pete

 

Well, I'm not certain that this is the culprit because I have not made it a priority yet to investigate, but I do see some odd anomalies in my implementation such as a recurring albeit intermittent bit that for some reason the GSX menu where you select pushback direction does not clear. And now that I have thought about it a bit I don't recall ever getting the "Do you want to request pushback" notice in my redirect, it only shows on the P3D screen. I normally have the P3D text messages turned off since I redirect to my app. 

So I can't say for sure if it's all related, thus looking forward to seeing if your new implementation of buffering will help.

If I can help in any way let me know...

James

Link to post
Share on other sites
13 hours ago, 737-SimGuy said:

If I can help in any way let me know...

Well, of course.  Please just use the version of FSUIPC6 supplied above and let me know if it does the job.

I see i omitted to describe the range of the timing allowed so I'll do it now:

TimeToDelayTexts=100 is the default

TimeToDelayTexts=0 turns it off, making FSUIPC act exactly as before

Otherwise the range allowed is 20 - 1000 (mSecs).

I'd like to know if the default value is a good choice, or whether it needs increasing or can be safely reduced. I know this will depend on what software is reading it. I mainly tested with P3D displays and menus generated by Lua plug-ins, because I've never had any problem with GSX or the like and my WideClient displays. I don't really have anything else that uses both the text lines and the menus.

It should be noted that this is just the maximum amount of time which a message, display window, or menu will be held back when they occur sooner than that after a different type of display (message, display window, or menu).

Pete

 

 

Link to post
Share on other sites
On 2/27/2021 at 1:00 AM, Pete Dowson said:

Well, of course.  Please just use the version of FSUIPC6 supplied above and let me know if it does the job.

I see i omitted to describe the range of the timing allowed so I'll do it now:

TimeToDelayTexts=100 is the default

TimeToDelayTexts=0 turns it off, making FSUIPC act exactly as before

Otherwise the range allowed is 20 - 1000 (mSecs).

I'd like to know if the default value is a good choice, or whether it needs increasing or can be safely reduced. I know this will depend on what software is reading it. I mainly tested with P3D displays and menus generated by Lua plug-ins, because I've never had any problem with GSX or the like and my WideClient displays. I don't really have anything else that uses both the text lines and the menus.

It should be noted that this is just the maximum amount of time which a message, display window, or menu will be held back when they occur sooner than that after a different type of display (message, display window, or menu).

Pete

 

 

Wilco. I finally have a few flights planned for Monday. Thanks Pete.I will report...

James

Link to post
Share on other sites

Hi Pete,
I did many tests over the weekend. I can not reproduce the error anymore. I did not do any modifications on my system. Same configuration as with the failed tests 3 days before. I can not explain that. No overwrite of messages vissible anymore. No [MessageFilters] used. Plain FSUIPC.ini + the debug features.

[GSX] Departure clearance requested
  1317421 ***DISP*** Text/menu type 1 broadcast
  1317421 LUA.1: text and menu function type 1 messages 1
  1317828 ### TEXT: 512 (Menu) From SimC, Duration 10.00, Flags 00000000, Len=183
  1317828      Select operator at Gate 345
  1317828      Select handling operator
  1317828      Condor
  1317828      Lufthansa  [GSX default choice]
  1317828      Aerogate
  1317828      EFM - Gesellschaft fur Enteisen & Flugzeugschleppen Munchen
  1317828      LOSCH Airport Service
  1317828 ***DISP*** Text/menu type 2 broadcast
  1317828 LUA.1: text and menu function type 2 messages 7
  1318953 ### TEXT_DESTROY: 512 (Menu) Result: 4, Flags 00000000
  1318953 ***DISP*** Text/menu type 2 clear broadcast
  1319640 ### TEXT: 512 (Menu) From SimC, Duration 30.00, Flags 00000000, Len=63
  1319640      GSX - Pushback Service
  1319640      Do you want to request Pushback?
  1319640      Yes
  1319640      No
  1319640 ***DISP*** Text/menu type 2 broadcast
  1319640 LUA.1: text and menu function type 2 messages 4
  1323406 ### TEXT: 257 (Static) From SimC, Duration 6.00, Flags 00000000, Len=40
  1323406
[GSX] Handling by LOSCH Airport Service
  1323406 ***DISP*** Text/menu type 1 broadcast
  1323421 LUA.1: text and menu function type 1 messages 1
  1329437 ### TEXT_DESTROY: 257 (Static) Result: 65540, Flags 00000000
  1329437 ***DISP*** Text/menu type 1 clear broadcast
  1349656 ### TEXT_DESTROY: 512 (Menu) Result: 65540, Flags 00000000
  1349656 ***DISP*** Text/menu type 2 clear broadcast
  1349890 ### TEXT: 257 (Static) From SimC, Duration 6.00, Flags 00000000, Len=23
  1349890
[GSX] Have a good trip
  1349890 ***DISP*** Text/menu type 1 broadcast
  1349890 LUA.1: text and menu function type 1 messages 1
  1355953 ### TEXT_DESTROY: 257 (Static) Result: 65540, Flags 00000000
  1355953 ***DISP*** Text/menu type 1 clear broadcast

 

I will of coures keep an eye on that. Pretty sure the problem will occur again.

Ruediger

Link to post
Share on other sites

Hi Pete,
I did many tests. Started with 100ms, down to 20ms in 10ms steps. Finally with 0ms. Restarted P3D for each test. The problem did not occur again. Then installed an older FSUIPC version (6.0.10), just to make sure that it is independend of the FSUIPC version. The problem did not occur anymore. I do not know the reason, it's a kind of magic because last week I had the problem almost with each run of a test. I am rather at a loss, because no change to the system have been made since last week. Stable configuration, no GSX update, tests performed always at the same airport and gate.

Ruediger

Link to post
Share on other sites
12 minutes ago, Delphi said:

I did many tests. Started with 100ms, down to 20ms in 10ms steps. Finally with 0ms. Restarted P3D for each test. The problem did not occur again. Then installed an older FSUIPC version (6.0.10), just to make sure that it is independend of the FSUIPC version. The problem did not occur anymore. I do not know the reason, it's a kind of magic because last week I had the problem almost with each run of a test.

Hmm. very strange.

Okay. Let's see whether 737-SimGuy gets any useful results.

Pete

 

Link to post
Share on other sites

Gentlemen,

I have done several tests using both default 100ms and also 50ms. With 50ms I get my current behavior of missing the "Do you wish to request pushback" message and also missing the menu clear messages occasionally. With 100ms everything appears to work correctly. I receive all messages and do not miss the clear messages.

I will continue to monitor it at 100ms in my coming flights and let you know if anything changes. So far it appears to have worked! I think 100ms is a good default for now.

My 2c. Thanks!

James

 

Link to post
Share on other sites
2 hours ago, 737-SimGuy said:

I have done several tests using both default 100ms and also 50ms. With 50ms I get my current behavior of missing the "Do you wish to request pushback" message and also missing the menu clear messages occasionally. With 100ms everything appears to work correctly. I receive all messages and do not miss the clear messages.

I will continue to monitor it at 100ms in my coming flights and let you know if anything changes. So far it appears to have worked! I think 100ms is a good default for now.

Okay, thanks. But I assume this is on the same PC as P3d, right? So if 50 mSec isn't quite enough, I'm wondering about WideClient access. Maybe it needs to be higher.

I have my GSX displays on a WideClient PC but i've never noticed any problem. Maybe i just don't use GSX enough. I don't suppose you use WideFS do you? If so, perhaps it would be possible to try your application on a Client?

Pete

 

 

Link to post
Share on other sites
34 minutes ago, Pete Dowson said:

Okay, thanks. But I assume this is on the same PC as P3d, right? So if 50 mSec isn't quite enough, I'm wondering about WideClient access. Maybe it needs to be higher.

I have my GSX displays on a WideClient PC but i've never noticed any problem. Maybe i just don't use GSX enough. I don't suppose you use WideFS do you? If so, perhaps it would be possible to try your application on a Client?

Pete

 

 

This IS on a client sir, via WideFS...

James

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.