Jump to content
The simFlight Network Forums

crwk78

Members
  • Posts

    34
  • Joined

  • Last visited

Everything posted by crwk78

  1. Or might be because I forgot to use UseSendInput=Yes at all! šŸ˜¬ Fixed!
  2. Hi, I am trying to get the keysend function over WideFS to work but no luck so far. I have the C key on the server set up to send parameter 1 when pressed and parameter 2 when released. On the client, this is set up so C is effectively held down for the duration it's pressed on the server. As it didn't seem to work, I set notepad as run1 and applied run1 to the keysend lines in wideclient.ini. I would expect C to type and continue to be typed on the client until the C key on the server is released, but still nothing. Screenshot attached, any ideas? Charlie K
  3. Hi Pete, hope you are well. On P3Dv4.5, Iā€™ve assigned the W key to ā€œToggle Water Rudderā€ in FSUIPC and am trying to monitor the Water Rudder statuses using the logging function of FSUIPC, offsets 2A78, 2A80 and 2A88 which are left rudder, right rudder and rudder handle position respectively. Tapping W doesnā€™t seem to be doing anything, the first two remain at 0 and the third is -16383? Where am I going wrong? Thanks Charlie K
  4. Thanks Paul, works fine now that I've added the Process () call.
  5. I pasted it in then deleted it as I couldn't put the cursor above the quote to type my message, then forgot to paste it back! Sorry, here it is:
  6. Hi, My code below works when I boot P3D and FSUIPC is detected as having connected (the label changes from default red to green). When I close P3D, the label remains green when I am expecting it to turn red again. Any ideas why this happens?
  7. Thanks John, very helpful. Your first suggestion worked. I also hadn't prefixed the filename with 'lua' in the [AUTO] section of fsuipc.ini. I think it'll work because I always start with traffic on, so it should always go off when I rotate, which is exactly what I need. PSXSeeconTraffic (through it's own settings) will turn its own AI on when I get airborne, so I should get a seamless switch, avoiding the live traffic when on the ground as it's not always very realistic and the default AI in the air for the same reason! 1008 with 0 might be a more robust option though. I'll look into your post above to see if I can adapt it to what I need. You have given me a good idea to use the gear up event (I'm assuming there is one) rather than the airborne one, as my pitch up attitude will mean I won't see the transition between AI modes. Many thanks again, Charlie
  8. Hi, I'm trying to write a LUA to turn off AI traffic when airborne. So far I have this which doesn't seem to be working. function trafficoff(offset, value) if value == 0 then ipc.control(1009) end event.offset("0336", "UB", "trafficoff") Any ideas where the problem is? CK
  9. Hi Pete, Itā€™s a 2yr old high-end PC. The file is created / time updated within a second of running MakeRwys so I donā€™t think itā€™s a time thing. Try deleting the file and running MakeRwys. In my case, the file is recreated (within a second), but it isnā€™t used in the output. If I run MakeRwys immediately after, the file is updated (within a second), and it is used this time round, and indeed for every further attempt. If you have teamviewer, I can demonstrate this for you, or send a quick video. Charlie K
  10. LorbyScenery.cfg is referred to in the P3D3 and P3D4 Lorby Readme document as the file created by LorbySceneryExport.exe. As a result I had assumed this was the LorbySceneryExport equivalent of Addon organizer's MakeRwys_scenery.cfg. In a good example of confirmation bias I then misread the MakeRwys User Manual sentence which says: "MakeRunways will then automatically use either Lorby-Si program to create a file called MakeRwys_Scenery.cfg in your P3D3 or P3D4 folder." I thought manual omitted an 'or' part of the sentence and should have read "MakeRunways will then automatically use either Lorby-Si program to create a file called MakeRwys_Scenery.cfg , or LorbySceneryExport to create a file called LorbyScenery.cfg , in your P3D3 or P3D4 folder". I've now re-read the sentence and realised it makes perfect sense without an 'or' bit in it. Now I understand that LorbyScenery.cfg is created for no reason (at least related to MakeRunways), it makes things a little more simple so I can summarise, at least on my PC that: 1) MakeRwys needs to be run in Admin mode to create and read the MakeRwys_Scenery.cfg and 2) MakeRwys does not use MakeRwys_scenery.cfg if there is not a file of that name in the directory when MakeRwys is run. In other words, when running MakeRwys for the first time, it creates the MakeRwys_scenery.cfg, but does not use it. If you run MakeRwys again immediately afterwards, it will read the MakeRwys_scenery.cfg. That makes me wonder if, on subsequent runs, it is reading the MakeRwys_scenery.cfg already in the directory or the one it has just created.. Sorry for any confusion!
  11. Hi Pete, some feedback on 4.86, all files in zip copied to C:\Prepar3d v4, Windows 10 Pro. Latest Lorby Addon Organizer installed as per above. First of all, MakeRwys_scenery.cfg is being created again, only when I run MakeRwys in admin mode, so the above issues are no longer relevant. MakeRwys.exe in normal mode: No MakeRwys_scenery.cfg created, no running of LorbySceneryExport.exe so no creation of LorbyScenery.cfg either. MakeRwys reads default scenery.cfg. MakeRwys.exe in admin mode: MakeRwys_scenery.cfg is created, LorbySceneryExport.exe appears to run but no creation of LorbyScenery.cfg. MakeRwys still reads default scenery.cfg. Manually running LorbySceneryExport.exe and then MakeRwys.exe in admin mode: LorbyScenery.cfg created with LorbySceneryExport.exe. MakeRwys_scenery.cfg created. MakeRwys reads MakeRwys_scenery.cfg. I then moved the LorbyScenery.cfg file out of the folder and ran MakeRwys (admin). It still reads the MakeRwys_scenery.cfg. I then replaced the LorbyScenery.cfg, removed the MakeRwys_scenery.cfg and ran MakeRwys (admin). Despite creating a new MakeRwys_scenery.cfg, it read the default scenery.cfg. I then ran MakeRwys again without any further changes and it read the MakeRwys_scenery.cfg. Can you replicate this? Charlie K
  12. I used the installer every time Iā€™ve installed it (about 5 times whilst troubleshooting today) both in normal and admin mode and always to the default path but that registry entry isnā€™t there. Strange. Can I just add it? The MakeRwys_scenery.cfg used to be there a while ago, I deleted it troubleshooting as MakeRwys wasnā€™t picking up addon scenery, thinking MakeRwys would just create a new one but it didnā€™t, so thatā€™s when I reinstalled Lorby, but with no success. Iā€™ll wait until the new versions come out and install afresh.
  13. Thanks for the info Pete. I'll get back to you on this when I'm next in the cockpit on Thursday.
  14. Hi Pete, I have MakeRwys v4.85 in the C:\Prepar3D v4 directory and AddonOrganizer v1.38b11 installed in C:\Users\Me\Documents\Prepar3D v4 Add-ons\Lorby-SI AddonOrganizer_P3D_V4. When I run MakeRwys (in both normal and admin modes), the MakeRwys_scenery.cfg is not created and the initial few lines of the Runways.txt file show: Make Runways File: Version 4.85 by Pete Dowson Reading (null) SCENERY.CFG ... CFG file being used is: "C:\ProgramData\Lockheed Martin\Prepar3D v4\SCENERY.CFG" Any ideas as to why this might be happening? Can you let me know the Lorby registry key that MakeRwys checks for so I can see if it is there? Thanks, Charlie K
  15. Hi Pete, Iā€™m not sure I can describe the issue with any more clarity than what Iā€™ve typed above already. There are no keypresses being made manually at VR (either once or any other amount of times). The T key is however set to traffic toggle in FSUIPC and the Prosim interface is set as per the screenshot above (except VR, not V1). I included it to show you the information you might need in order to make an assessment of what is happening. With all the above being the case, the FSUIPC log displays as above. It is possible that some info is missing as I may have had selective logging enabled. I am away from the PC so donā€™t have access to the log but on removing the keypress assignment as I recall the log still indicates the control being sent twice but only with the following lines: Setting Airlineļ»æļ»æļ»æļ»æ traffic densitļ»æy = 0 Setting Airlineļ»æļ»æļ»æļ»æ traffic densitļ»æy = 1ļ»æ0ļ»æ0ļ»æ Finally, when I remove the Prosim assignment, no traffic related changes are made at any time unless I hit the T key. I sent a ticket to Prosim on the day I started this thread, they requested the FSUIPC log which I sent, but no further reply so far. I expect it is a Prosim issue but Iā€™m still interested to see why it is sending a control (twice) and FSUIPC is receiving a keypress (twice). The fact that Prosim doesnā€™t know the FSUIPC keypress assignments makes it even more odd. I know youā€™re a Prosim user, are you able to recreate the problem? Charlie K
  16. It is attached to the V1 gate here but I was getting the same issue so moved it to the VR just to check.
  17. Hi Pete, Yes, I also have Traffic Toggle assigned to the T key which I have set on a custom keyboard, giving me a further method to toggle traffic, but Iā€™m not pressing T at VRotate, or any other keys (I have both hands on the yoke!). Prosim is sending 1009 once at VRotate so the control should only be sent once, so AI should be switched off if it was on previously (or vice versa). Unless Iā€™m misunderstanding something.. Have a great holiday! Charlie K
  18. Hi Pete, I have set Prosim to send "0x3110 = 1009" when the VRotate gate has been reached (to turn AI traffic off when airborne). I always start the sim with AI traffic on so that the control sent will turn AI traffic off at VR. However, at VR I am seeing the screen go black, the traffic loading bar appear and then a fully AI populated airport, almost as if the control sent is requesting 100% traffic rather than a toggle from 100% to 0%, or the traffic is toggled twice (to 0% and then back to 100%). The FSUIPC log shows that it may be the latter (0% then straight back to 100%) but I'm not sure: 1269047 KEYDOWN: VK=84, Waiting=0, Repeat=N, Shifts=0 1269047 FSUIPC Control Action: Ctrl=1009, Param=0 1269047 .... Delayed to be executed synchronously 1269047 .. This key is programmed in FSUIPC4 'Keys' options 1269047 KEYUP: VK=84, Waiting=0 1269062 FSUIPC Control Action: Ctrl=1009, Param=0 1269062 Setting Airline traffic density = 0 1269953 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16208 (0x00003f50) KOHLSMAN_SET 1271062 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16208 (0x00003f50) KOHLSMAN_SET 1272172 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16208 (0x00003f50) KOHLSMAN_SET 1273203 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16208 (0x00003f50) KOHLSMAN_SET 1273734 KEYDOWN: VK=84, Waiting=0, Repeat=N, Shifts=0 1273734 FSUIPC Control Action: Ctrl=1009, Param=0 1273734 .... Delayed to be executed synchronously 1273734 .. This key is programmed in FSUIPC4 'Keys' options 1273734 KEYUP: VK=84, Waiting=0 1273734 FSUIPC Control Action: Ctrl=1009, Param=0 1273734 Setting Airline traffic density = 100 Any ideas what the issue might be? Charlie K
  19. I've been looking through the List of Controls PDF file but can't find the control to toggle AI Traffic on and off. I managed to find the AI Labels control (66199) but not the control to toggle the AI itself. Can someone tell me what it is? Thanks!
  20. Hi Pete, unfortunately your reply makes me none the wiser! I saw what you said and therefore put 3114 first and 3110 second in the Prosim config page. I was trying to point out that just because that's the order I've put them in, I don't know if that's the order Prosim necessarily sends them. I cannot find the number "3114" in any of the .pdf files you supply with the program. I can see that 3110 is split into two, the control and the parameter, but 3114 is not mentioned. To which documentation do you refer? At the risk of being completely wrong and berated for it (you've spent years as the expert on this, I have not) does the value go before the x in the Prosim menu? So if the control is 66482 should the second entry above be 66482x3110? And if that is the format, what goes before the x3114 as with a toggle I'd be sending different values each time (on and then off or 1 and then 0 etc).. Cheers, CK
  21. Thanks Pete for quick reply, Prosim can send two offsets for one trigger but I'm not sure about the order in which it sends them. I can see what 3110 is but what is 3114? Also, it doesn't allow me to send a value, or do I assign the value to the offset in FSUIPC? CK
  22. Hi, I've done some searching but can't find an answer so far. RAAS Pro by FS2Crew allows the RAAS system to be turned on and off using the Water Rudder Toggle control (Ctrl+W by default). I want to be able to send this keystroke to P3D when my Prosim AC Power gate is active (so that RAAS is active when AC power is on and inactive when AC power is off). Prosim doesn't allow a gate to send keystrokes to P3D directly, but it does allow a gate to send an FSUIPC offset. They've told me I can set a spare FSUIPC offset to be sent when the AC Power gate is active and link this offset in FSUIPC to the Ctrl+W keystroke. Prosim Options are: FSUIPC 8 BIT U FSUIPC 8 BIT S FSUIPC 16 BIT S FSUIPC 16 BIT U FSUIPC 32 BIT S FSUIPC 32 BIT U FSUIPC FLOAT 32 FSUIPC FLOAT 64 I have worked out how to get a keystroke to send a FSUIPC offset, but I need to know how to do it the other way round.. Thanks in advance for any assistance. CK
×
×
  • 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.