Jump to content
The simFlight Network Forums

aua668

Members
  • Posts

    381
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by aua668

  1. Hi, Some things you might check, if you have an ON/OFF switch but only found a toggle command in the command list: Check, if there is an corresponding offset available, which you could use to invoke set/clear instead toggling If the offset is read-only, you might consider offset conditions in your button programming Check if there are Lvars available in the specific plane, which you could use to set/clear the respective switch If nothing else worked, you could check, if there are distinct click spots available in the gauge for on/off. Or if on/off is triggered by different mouse buttons. In that case you could use mouse macros, if the gauge is supporting it. A good starting point is also to check, if there is a LINDA module available for that specific plane. Maybe you get there a hint, how to operate the specific switch. Rgds Reinhard
  2. Hi, A better way to toggle these switches is by setting the following Lvars to 0 or 1: L:AB_PDS_Eng1Master L:AB_PDS_Eng2Master You can do this either by a small LUA script or by creating a "normal" macro toggling these variables. See page 39 in the Advanced User Manual. Then you simply can assign this macro to your button. Also many other switches can be operated by that method. It's way better compared to the mouse macro, as this method works across engine variants on all A3xx planes from AS. Rgds Reinhard
  3. Hi, There is an easy solution, which I use since the beginning: When I download the ZIP file, I save it as FSUIPC_xxx.zip (with xxx being the version). By that I always know, which version I am installing and I can step back if there is a problem with the latest release (which did not happen as the tool is perfect). So this can be solved easily. Rgds Reinhard
  4. John, Thanks - no hurry and prepare for the future 😉 Rgds Reinhard
  5. Dear Pete, Dear John, Is there any chance to get in a future release of FSUIPC access to these Simconnect functions: SimConnect_DockView SimConnect_UndockView The reason: If you want to move views (e.g. panel pop-ups) to different screens dynamically in a multi-monitor environment, they must be unlocked. While you can save such views in P3D 4.5 on the main monitor as undocked window, this doesn't work for example on already undocked windows on a secondary monitors. There these panel views are always docked - even if you save the scenario as undocked. Loading them dock these views always. Manually I can unlock them and then move them with your ext.position function in LUA. But for unlocking them I have no function. Best regards Reinhard
  6. Hi, Thanks for sharing the LUA. Now I know, where you are coming from. You are using the relatively old FSX NumPad Control Utility from Al Klayton, which can be found here: https://simviation.com/1/browse-Utilities-65-5?mark=49328#49328 This is a set of LUA files, which provide the possibility to enter values for the radios via the NumPad. But checking the ZIP file I found, that there is also an ADF routine included to set the ADF. Why aren't you using this routine? Has your aircraft two ADFs (ADF1 and ADF2)? Be aware, that these modules typically will work with standard airplanes. If you use a specific add-on aircraft with an own implementation of the radios, these scripts will not work. And in the standard ADF implementation of FSX there was only one ADF implemented. ADF1 and ADF2 has been added later, as far as I remenber. If you want to adopt these routines, you should check the routine"NpCkeyData.lua". There the actual numbers are transferred to the respective radios via ipc.control calls. So I assume, you have to learn LUA programming to extend the functionality of these modules 😉 Or you contact Al Klayton, if he is still around in the flight simulator scene. Another option is to buy some hardware add-on (Saitek radio panel or similar). You will see, that this makes more fun and realism than typing the numbers via the keypad. Rgds Reinhard
  7. Hi, If you could share the file "NpCsetOBS.lua" here, there is a good chance to modify it in a way that you can use it. Rgds Reinhard
  8. Hi, Thomas answered already perfectly - the screenshot showed the misunderstanding clear. For the OBS: In that case you are triggering a LUA routine "NpCsetOBS.lua". That's a complete different way to trigger an action. You could also experiment with the Inc and Dec commands to check, if the ADF is reacting. If this is an commercial add-on plane, it's not always guaranteed, that they use the standard simulator functionality in their gauges. Rgds Reinhard
  9. Hi, You did not mention, which simulator you are using. In P3D V4 you have thre controls for ADF Card: 65882 ADF_CARD_DEC 65881 ADF_CARD_INC 66039 ADF_CARD_SET Which parameter did you use for ADF_CARD_SET? Please show a screenshot, how you did configure your key. RGDS Reinhard
  10. Hi, There is a double-quote missing in your command: handle, error= ext.run("C:\\SIOC.exe", "EXT_KILL"). Rgds Reinhard
  11. Hi, Please check the section about compund button conditions in the advanced user manual. There you should find the information you are looking for. Rgds Reinhard
  12. Jason, Here in text form: Offset 0BC0 WORD Elevator trim control input: –16383 to +16383 Offset 0BC2 WORD Elevator trim indicator (follows input) Rgds Reinhard
  13. Hi, I did additional tests with different InitDelay parameter values in the INI file to check, if the behaviour is changing. But this made no difference at all. Then I eliminated the call to vpilot, which is the entry before the errors occur. But the errors still occured. Rgds Reinhard
  14. Hi, I read your post in the E-Jet forum. Now I understand your request. Let's hope they improve anyhow the FDE of the plane, which is not very realistic at the moment, with the planned service pack. Rgds Reinhard
  15. Hi, What should trigger this action? airspeed, time, weather, taste of the beer you are drinking? Maybe you can specify your need a little bit more excactly. LUA functions can extend and retract flaps by one notch using for example the ipc.controls for: 65758 FLAPS_INCR 65759 FLAPS_DECR Rgds Reinhard
  16. Hi, One interesting observation: Scotfleiger gets different warnings compared to me. I also do not get exactly the same warnings all the time, but they are often quite similar. So it's maybe timing dependent. When you load the plane, Aerosoft runs some scripts for initializing the panel state to the user-configured preference (cold & dark, ready to fly, etc.). Also the Navigraph database is loaded etc. And they use simconnect too. Maybe there is something blocking your reading and you just have to wait a little bit before running your initialization. Just a guess without knowing the details. I enclose my INI and log files for your reference including also two logs from the A320, my flight file and the A320 FSUIPC profile. Rgds Reinhard A320_Logs.zip
  17. Hi Pete, As it has no side effect, it's low priority. All connections I need are working. So no urgent issue (but maybe interesting to know, where these strange messages are coming from). For the connection of my hardware to the A320 I only use Lvars and standard FSUIPC offsets, if the A320 uses them. So I make no direct use of SimConnect functionalities. Suppressing the messages is also a solution 😉 Rgds Reinhard
  18. Hi, I updated to 5.153, did a test with the A320 and then with the standard A36 from P3D. Only with the A320 the errors occured. The parameter NoWeatherAtAll=Yes I had already in my INI file. I also tested with the E195 from Feelthere - no errors in the log. Rgds Reinhard
  19. Hi, I will update to the latest version as I normally always do. Missed that update obviously during the Xmas holidays. Too much sweets and wine with the family 😉 I don't use LINDA, but I use self-developed LUA modules for interfacing my planes to my GoFlight hardware. With other planes (eg the Majestic Dash Q400) I don't see these messages). With the Q400 there always have been three other strange messages from begining of the plane and in all FSUIPC vrsions: 80063 Exception 3 "UNRECOGNIZED_ID", Ref 2774, Index param 1 on write SetData for "RECIP ENG FUEL FLOW:1" 80063 Exception 3 "UNRECOGNIZED_ID", Ref 2775, Index param 1 on write SetData for "RECIP ENG FUEL FLOW:2" 80063 Exception 3 "UNRECOGNIZED_ID", Ref 2776, Index param 1 on write SetData for "RECIP ENG FUEL FLOW:3" But these messages always have been there. I once reported them to Majestic, but they had no idea. They also had no negative side effect. So the common thing in the above case is obviously the A320 Pro. The tests I will do on the weekend. Rgds Reinhard
  20. Hi, Just checked my log and it contains also these errors: 121906 Exception 25 "ILLEGAL_OPERATION", Ref 433, Index param -1 on read AddData for "AIRSPEED MACH" 121906 Exception 25 "ILLEGAL_OPERATION", Ref 434, Index param -1 on read AddData for "TOTAL AIR TEMPERATURE" 121953 Exception 25 "ILLEGAL_OPERATION", Ref 435, Index param -1 on read AddData for "NUM FUEL SELECTORS" 121953 Exception 25 "ILLEGAL_OPERATION", Ref 436, Index param -1 on read AddData for "UNLIMITED FUEL" 122015 Exception 25 "ILLEGAL_OPERATION", Ref 437, Index param -1 on read AddData for "FUEL TOTAL CAPACITY" 122015 Exception 25 "ILLEGAL_OPERATION", Ref 438, Index param -1 on read AddData for "FUEL TANK CENTER2 LEVEL" 122078 Exception 25 "ILLEGAL_OPERATION", Ref 439, Index param -1 on read AddData for "FUEL TANK CENTER2 CAPACITY" 122078 Exception 25 "ILLEGAL_OPERATION", Ref 440, Index param -1 on read AddData for "FUEL TANK CENTER3 LEVEL" 122140 Exception 25 "ILLEGAL_OPERATION", Ref 441, Index param -1 on read AddData for "FUEL TANK CENTER3 CAPACITY" 122140 Exception 25 "ILLEGAL_OPERATION", Ref 442, Index param -1 on read AddData for "FUEL TANK EXTERNAL1 LEVEL" 122187 Exception 25 "ILLEGAL_OPERATION", Ref 443, Index param -1 on read AddData for "FUEL TANK EXTERNAL1 CAPACITY" 122187 Exception 25 "ILLEGAL_OPERATION", Ref 444, Index param -1 on read AddData for "FUEL TANK EXTERNAL2 LEVEL" 122281 Exception 25 "ILLEGAL_OPERATION", Ref 445, Index param -1 on read AddData for "FUEL TANK EXTERNAL2 CAPACITY" 122281 Exception 25 "ILLEGAL_OPERATION", Ref 446, Index param -1 on read AddData for "FUEL TOTAL QUANTITY" 122343 Exception 25 "ILLEGAL_OPERATION", Ref 447, Index param -1 on read AddData for "FUEL SELECTED QUANTITY" 122343 Exception 25 "ILLEGAL_OPERATION", Ref 448, Index param -1 on read AddData for "FUEL TOTAL QUANTITY WEIGHT" 122390 Exception 25 "ILLEGAL_OPERATION", Ref 449, Index param -1 on read AddData for "ESTIMATED FUEL FLOW" 122390 Exception 25 "ILLEGAL_OPERATION", Ref 450, Index param -1 on read AddData for "GPS DRIVES NAV1" 122453 Exception 25 "ILLEGAL_OPERATION", Ref 451, Index param -1 on read AddData for "EMPTY WEIGHT" 122453 Exception 25 "ILLEGAL_OPERATION", Ref 452, Index param -1 on read AddData for "MAX GROSS WEIGHT" 122500 Exception 25 "ILLEGAL_OPERATION", Ref 453, Index param -1 on read AddData for "PAYLOAD STATION COUNT" 122500 Exception 25 "ILLEGAL_OPERATION", Ref 454, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:1" 122547 Exception 25 "ILLEGAL_OPERATION", Ref 455, Index param -1 on read AddData for "PAYLOAD STATION NAME:1" 122547 Exception 25 "ILLEGAL_OPERATION", Ref 456, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:2" 122578 Exception 25 "ILLEGAL_OPERATION", Ref 457, Index param -1 on read AddData for "PAYLOAD STATION NAME:2" 122578 Exception 25 "ILLEGAL_OPERATION", Ref 458, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:3" 122625 Exception 25 "ILLEGAL_OPERATION", Ref 459, Index param -1 on read AddData for "PAYLOAD STATION NAME:3" 122625 Exception 25 "ILLEGAL_OPERATION", Ref 460, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:4" 122672 Exception 25 "ILLEGAL_OPERATION", Ref 461, Index param -1 on read AddData for "PAYLOAD STATION NAME:4" 122672 Exception 25 "ILLEGAL_OPERATION", Ref 462, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:5" 122703 Exception 25 "ILLEGAL_OPERATION", Ref 463, Index param -1 on read AddData for "PAYLOAD STATION NAME:5" 122703 Exception 25 "ILLEGAL_OPERATION", Ref 464, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:6" 122750 Exception 25 "ILLEGAL_OPERATION", Ref 465, Index param -1 on read AddData for "PAYLOAD STATION NAME:6" 122750 Exception 25 "ILLEGAL_OPERATION", Ref 466, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:7" 122781 Exception 25 "ILLEGAL_OPERATION", Ref 467, Index param -1 on read AddData for "PAYLOAD STATION NAME:7" 122781 Exception 25 "ILLEGAL_OPERATION", Ref 468, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:8" 122828 Exception 25 "ILLEGAL_OPERATION", Ref 469, Index param -1 on read AddData for "PAYLOAD STATION NAME:8" 122828 Exception 25 "ILLEGAL_OPERATION", Ref 470, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:9" 122890 Exception 25 "ILLEGAL_OPERATION", Ref 471, Index param -1 on read AddData for "PAYLOAD STATION NAME:9" 122890 Exception 25 "ILLEGAL_OPERATION", Ref 472, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:10" 122937 Exception 25 "ILLEGAL_OPERATION", Ref 473, Index param -1 on read AddData for "PAYLOAD STATION NAME:10" 122937 Exception 25 "ILLEGAL_OPERATION", Ref 474, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:11" 122968 Exception 25 "ILLEGAL_OPERATION", Ref 475, Index param -1 on read AddData for "PAYLOAD STATION NAME:11" 122968 Exception 25 "ILLEGAL_OPERATION", Ref 476, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:12" 123015 Exception 25 "ILLEGAL_OPERATION", Ref 477, Index param -1 on read AddData for "PAYLOAD STATION NAME:12" 123015 Exception 25 "ILLEGAL_OPERATION", Ref 478, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:13" 123062 Exception 25 "ILLEGAL_OPERATION", Ref 479, Index param -1 on read AddData for "PAYLOAD STATION NAME:13" 123062 Exception 25 "ILLEGAL_OPERATION", Ref 480, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:14" 123093 Exception 25 "ILLEGAL_OPERATION", Ref 481, Index param -1 on read AddData for "PAYLOAD STATION NAME:14" 123093 Exception 25 "ILLEGAL_OPERATION", Ref 482, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:15" 123140 Exception 25 "ILLEGAL_OPERATION", Ref 483, Index param -1 on read AddData for "PAYLOAD STATION NAME:15" 123140 Exception 25 "ILLEGAL_OPERATION", Ref 484, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:16" 123172 Exception 25 "ILLEGAL_OPERATION", Ref 485, Index param -1 on read AddData for "PAYLOAD STATION NAME:16" 123172 Exception 25 "ILLEGAL_OPERATION", Ref 486, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:17" 123234 Exception 25 "ILLEGAL_OPERATION", Ref 487, Index param -1 on read AddData for "PAYLOAD STATION NAME:17" 123234 Exception 25 "ILLEGAL_OPERATION", Ref 488, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:18" 123281 Exception 25 "ILLEGAL_OPERATION", Ref 489, Index param -1 on read AddData for "PAYLOAD STATION NAME:18" 123281 Exception 25 "ILLEGAL_OPERATION", Ref 490, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:19" 123343 Exception 25 "ILLEGAL_OPERATION", Ref 491, Index param -1 on read AddData for "PAYLOAD STATION NAME:19" 123343 Exception 25 "ILLEGAL_OPERATION", Ref 492, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:20" 123406 Exception 25 "ILLEGAL_OPERATION", Ref 493, Index param -1 on read AddData for "PAYLOAD STATION NAME:20" 123406 Exception 25 "ILLEGAL_OPERATION", Ref 494, Index param -1 on read AddData for "PAYLOAD STATION WEIGHT:21" It's with P3D 4.5 latest version, FSUIPC Version 5.152 and with the Aerosoft A320. Can't remember, that I have seen this before. There was a .NET update some days ago for WIN10. Rgds Reinhard
  21. Hi, Yes - it's the same. I also tried to switch to summrer season, where the rolling coefficient is different. Rgds Reinhard
  22. Hi, I made now a test in LOWW (FlyTampa scenery). No weather addon activated (normally I use ActiveSky). I started the APU and then the engine. I entered only origin and destination but did not enter the complete flightplan. I started aligning IRS. I enclosed a ZIP file with the following content: Screenshot done after engine start - note the white line on the bottom (2020-01-16 23_50_47-P3D.jpg) Screenshot of the panel showing the engine setting (2020-01-16 23_51_13-P3D.jpg) Screenshot 6 minutes later - the plane has moved forward and the white line is not visible anymore (2020-01-16 23_56_52-P3D.jpg) The flight files saved (E195_LOWW.xxx) 3 screenshots (engine 1, engine 2 and ground dynamics) read out on a second PC Rgds Reinhard E195_LOWW.zip
  23. Hi, I will save a FLT tomorrow evening, when I am back at home. Thanks for checking this issue. Btw: I did some search and found references, that some users of the AS CRJ and some PMDG planes experienced a similar phenomenon. Maybe it's a simulator issue, ... A solution was not documented. Rgds Reinhard
  24. Hi, No ground friction addon or similar. in use here The last time I used this type of tools has been with FSX. But this is now long ago 😉 I also don't use special tweaks in my P3D config file. I only use FSUIPC and some self developed LUA modules to interface to my GoFlight hardware. For toggling the parking brake I use the standard simulator command. I am using several other aircraft (Majestic Q400, AS A3xx, AS Twin Otter, Cranedo A36, etc.). But with all of them this problem doesn't exist. And it makes no difference, if I set the parking brake or if I use the toe brakes fully engaged. It's a very slow movement so in the first moments you don't detect it. But when I did my first online VATSIM flight, I needed a lot longer than normal for preparing the aircraft, as I am not yet so experienced with this plane. And suddenly I detected, that I have moved half way onto the taxi lane in front of me. Best regards Reinhard
  25. Hi, It's definitely not a controller issue. I have calibrated my throttles with an idle zone via FSUIPC. The value is always on idle, which I can read out externally with an app on a second PC. It's moving very slow and therefore you will not detect it immediately - but if you are starting the engines and wait for 10-15 minutes with parkin brakes set (which could happen on a very busy airport before you get the takeoff clearance), you will see, that you are moving. As a hint: look on the bottom of your screen. The lowest pixels will show, that you are moving forward. It's the E195 I am using. N1 shows around 23 in idle state. The axis value for throttle 1 and 2 is zero. Rgds Reinhard
×
×
  • 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.