Jump to content
The simFlight Network Forums

All Activity

This stream auto-updates     

  1. Today
  2. Peabody

    Airport Operations Questions Tower 3D

    But I'm still in training, I'm not full Pedantic yet πŸ€”
  3. Yesterday
  4. hexzed

    Airport Operations Questions Tower 3D

    You also have to change your name to Pedantic P, and think of some type of coded (virtual) handshake πŸ˜„
  5. Braf123456

    Airport Operations Questions Tower 3D

    oh ok thanks i like your profile pic
  6. Pedantic G

    Airport Operations Questions Tower 3D

    Maybe we can get Vic to give us special emoji's to use as a code!!! 🀣
  7. Pedantic G

    Airport Operations Questions Tower 3D

    It's just a bit of fun and banter! Official meaning of PEDANTIC is: "excessively concerned with minor details or rules; overscrupulous. πŸ˜‰
  8. Braf123456

    Airport Operations Questions Tower 3D

    what is a Pedantic club
  9. thanks ik we have a couple max planes i was just wondering about neos
  10. Peabody

    Airport Operations Questions Tower 3D

    Thanks Pedantic G LOL. I just enjoy learning. I was just listening to KLAS (again) and they had a go around, and then told a departing plane it just lost its "slot" for San Diego because of the delay caused by the go around, so he had to hold for about 10 minutes.........who can figure all this out? BTW, do we get secret decoder rings in the Pedantic club?
  11. No idea matey. Depends on the developers appetite to do this or not and their other priorities.
  12. Pedantic G

    Airport Operations Questions Tower 3D

    At 67 Peabody, you are entitled to be Pedantic! Nice to know there is another person that likes to get things as accurate as you can even if it's only a game! Welcome to the Pedantic club matey 😁
  13. Peabody

    Airport Operations Questions Tower 3D

    Thanks for the info, appreciated it.
  14. Somehow missed that 'end' when copy -pasted the code here. I actually already did the test with eliminating the com port, but just to be sure that i am not missing something, i commented those parts again --dev = com.open("COM3",115200,0) and --com.write (dev, sen) and it crashed again. Then i commented all --dev = com.open("COM3",115200,0) --com.write (dev, sen)ο»Ώ --ipc.log(sen) --ipc.display(sen) but crashed again. And then i did the opposite test - re-enabled the com port, but exchanged 02C8 offset with another one extracting vertical speed data 030C ( i know that one works ), also commented 3BE7 vsOne = ipc.readSD("030C"ο»Ώ) --vsiFail = ipc.readUB("3BE7") and inadvertent FS9 crashes stopped. Both 02C8 and 3BE7 , when used within Lua plug-in (in pair or on their own) are making the problem to re-appear . And there are some more like them. The problem is really really strange one . The 'clear time' before FS9 crashes is getting much shorter, when more of those are placed and called within the same lua plug-in, compared to occasions when only one sensitive offset is used.
  15. Yes, only three positions per switch. OFF, ON, X-FEED Just to be sure I understand what you are saying regarding logging both together. I will setup and use the macro as shown below for future testing with only one log. [Macros] 1=TankSelect1/0=C65958 2=TankSelect1/1=C65955 3=TankSelect1/3=C65957 4=TankSelect2/0=C65958 5=TankSelect2/1=C65955 6=TankSelect2/2=C65957 Chris
  16. It seems that the switch is returning 0, 1, 2 and 3. My code isn't inventing those numbers, they are what arrives. Are there definitey only 3 positions? If so there's something a bit wrong with the device or its firmware. I don't know about the FSUIPC logs, but I think your log names for the PFChid program are the wrong way around. As far as I can see, the Tankselect2 log is for TackSelect1 and vice versa. Otherwise nothing make sense! It is odd. But now we have results for both switches, it looks like it only accepts 0 and 1. The return' for 2, and that odd 3, give the 'default' without the /n part. I can look for exactly that now we have some details. Maybe the macro coding was only ever tastest with only two positioned switches For any other logs, please do both together, not separately. The way you've done it makes it harder working it all out for me. it might be clearer for you like that, but best for you to test as you wish without any macros, and for me with the full set of macros. I'll be looking at this in the morning. Pete
  17. when will we get the neo planes in the game
  18. Okay. I need to know first whether it still crashes if you comment out the com stuff (com.open abd com-write lines). Otherwuse I would need to find some way of making one of my COM ports valid. Also, I assume there's and 'end' at the end? Pete
  19. manu4life

    Configuration crash

    I;m still getting the exact same error message 😞 any other suggestions?
  20. flying-w

    Configuration crash

    That file is broken. Please try this replacement: TrafficBoardFrontEnd.exe.config Thanks Simon
  21. I did not include /3 in the macro, because the documentation says to use /0 for the first switch position, /1 for the second switch position and /2 for the third switch position. We see that TankSelect1 it is call position 3, but it should be 2. Unlike the TankSelect2 switch which calls for 0, 1, 2 positions as documented for that type of switch. I can change the macro for TankSelect1 from /2 to /3, but that seems not to address the issue why is it not calling for position 2. I agree TankSelect1 positions 0 and 1 work perfectly πŸ™‚ I agree πŸ™‚ I am curious why the log shows "PFC:TankSelect2" and not "PFC:TankSelect2/2" and the same issue applies to TankSelect1 except for the fact TankSelect1 is using 3 and not 2 for the third physical switch position. I have not assigned any macros to the TankSelect2 currently. I have been logging TankSelect2 without macros to understand what it was doing. Changed I have now run two tests: TankSelect1 Test with the following macro [Macros] 1=TankSelect1/0=C65958 2=TankSelect1/1=C65955 3=TankSelect1/3=C65957 TankSelect2 Test with the following macro [Macros] 1=TankSelect2/0=C65958 2=TankSelect2/1=C65955 3=TankSelect2/2=C65957 In both cases the Tank switch that is not being tested, does not have any macros assigned. Chris FSUIPC5-TankSelect2 Test.log PFChid64-TankSelect2 Test.log FSUIPC5-TankSelect1 Test.log PFChid64-TankSelect1 Test.log
  22. Hi Pete, What can i say, thanks a lot for this new feature. For me FSUIPC5 it's more than fine πŸ˜„ Days or weeks doesn't matter, take your time. Thanks again for the help.
  23. That one below is crashing FS9 almost instantly after the start: vsOneOld = 2001 dev = com.open("COM3",115200,0) while 1 do vsOne = ipc.readSD("02C8") vsiFail = ipc.readUB("3BE7") vsOne = (vsOne*60*3.28084)/256 if ( vsiFail == 1 ) then vsOne = 0 elseif (vsOne > 2000) then vsOne = 2000 elseif (vsOne < -2000) then vsOne = -2000 end vsOne = vsOne + 2000 if (vsOne ~= vsOneOld) then sen = string.format ("vs%04d", vsOne) com.write (dev, sen) --ipc.log(sen) ipc.display(sen) vsOneOld = vsOne end ipc.sleep(20) I hope , that i am not causing too much trouble 😞 The airplane i am using is the default Cessna172 . PS- I checked just now , it happens also with the rest of the default airplanes selected
  24. Pete Dowson

    LUA Script and GSX Menu

    With event.textmenu you'd be able to read the menus, the item placing in the menu itself, and, possibly just as importantly, the textual prompts outside the menu. A plug-in could handle other programs with menus too, whether they have L:Vars you can use or not. So, I've decided it might be very useful and so I am adding this capability now. It will be in the next update for FSUIPC5 (only). Not sure when yet -- there are other things we are doing -- but probably within days rather than weeks. Pete
  25. Hi Pete, Yes, I just rely on L:Vars, not in the text of the GSX Menu. I tried the event.ο»Ώtextmenu, but it gives me one a "null" error, so i see that this is a WideClient function (it's documented, my bad). Well, if you are able to do that, for me would be great and be very appreciated, because my goal is to do something like this to call boarding/deboarding and all other stuff: ipc.keypressplus(123, 3, 4) -- CTRL + Shift + F12 while GSXMenuflag == 0 do -- Wait until GSX Menu appears ipc.sleep(100) end ipc.keypressplus(49, 0, 4)ο»Ώ -- Press 1 This would make almost one invisible GSX Menu πŸ™‚
  26. crbascott

    Airport Operations Questions Tower 3D

    I think it is either controller preference, the controller confirming a possible deviation from the chart, or combined frequencies. For example while I'm typing this post this morning everyone (regardless of departure runway and departure heading) was being sent to 125.9. There appeared to be only one tower controller and I assume only one active departure controller. FYI - there were several STAAV8 departures which would normally be sent to the 133.95 departure frequency.
  27. Pete Dowson

    LUA Script and GSX Menu

    Actually, I don't see any reason I cannot add it to the FSUIPC5 Lua event library. There just never seemed to be any point before. I can implement that for the next 5.14 update. So, you don't read the text of the menus, you just relay on the L:Vars? The event.textmenu facility would give you texts as well, not just for menus but also Simconnect messages and contents of message windows. Pete
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×

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.