Jump to content
The simFlight Network Forums

aua668

Members
  • Posts

    381
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by aua668

  1. Pete, My setup: WIN7/64, P3D 3.4 with latest hotfix.I have the Saitek Yoke with TQ and a second TQ and the GF TQ6. Windows 7 Home Premium 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1) Prepar3D.exe version = 3.4.22.19868 First here my FSUIPC.INI entries and the joystick scan log BEFORE I changed to the new version: OLD: ==== [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Yoke 0.GUID={35A598E0-AAF5-11E1-8002-444553540000} 1=TQ6 1.GUID={317A1330-B07D-11E1-800C-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={7EC7D4F0-B1C3-11E1-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={35A598E0-AAF5-11E1-8001-444553540000} R=Saitek Pro Flight Rudder Pedals Y=Saitek Pro Flight Yoke T=Saitek Pro Flight Quadrant G=TQ6 296 ---------------------- Joystick Device Scan ----------------------- 296 Product= Saitek Pro Flight Rudder Pedals 296 Manufacturer= Saitek 296 Vendor=06A3, Product=0763 (Version 1.0) 296 Serial Number= 296 Product= Saitek Pro Flight Yoke 296 Manufacturer= Saitek 296 Vendor=06A3, Product=0BAC (Version 3.2) 296 Serial Number= 296 Product= Saitek Pro Flight Quadrant 296 Manufacturer= Saitek 296 Vendor=06A3, Product=0C2D (Version 2.0) 296 Serial Number= 296 Product= TQ6 296 Manufacturer= GoFlight 296 Vendor=09F3, Product=0200 (Version 2.0) 296 Serial Number= 00080 7 296 ------------------------------------------------------------------- Then I changed to the new version: NEW: ==== [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Rudder Pedals 0.GUID={35A598E0-AAF5-11E1-8001-444553540000} 1=Saitek Pro Flight Yoke 1.GUID={35A598E0-AAF5-11E1-8002-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={7EC7D4F0-B1C3-11E1-8001-444553540000} 3=TQ6 3.GUID={317A1330-B07D-11E1-800C-444553540000} R=Saitek Pro Flight Rudder Pedals Y=Saitek Pro Flight Yoke T=Saitek Pro Flight Quadrant G=TQ6 266 ---------------------- Joystick Device Scan ----------------------- 266 Product= Saitek Pro Flight Rudder Pedals 266 Manufacturer= Saitek 266 Vendor=06A3, Product=0763 (Version 1.0) 266 Serial Number= 266 Assigned joystick id 0 (fixed Registry) 281 GUID= {35A598E0-AAF5-11E1-8001-444553540000} 281 Product= Saitek Pro Flight Yoke 281 Manufacturer= Saitek 281 Vendor=06A3, Product=0BAC (Version 3.2) 281 Serial Number= 281 Assigned joystick id 1 (fixed Registry) 281 GUID= {35A598E0-AAF5-11E1-8002-444553540000} 281 Product= Saitek Pro Flight Quadrant 281 Manufacturer= Saitek 281 Vendor=06A3, Product=0C2D (Version 2.0) 297 Serial Number= 297 Found correct joystick Id 2 297 GUID= {7EC7D4F0-B1C3-11E1-8001-444553540000} 297 Product= TQ6 297 Manufacturer= GoFlight 297 Vendor=09F3, Product=0200 (Version 2.0) 297 Serial Number= 00080 7 297 Assigned joystick id 3 (fixed Registry) 297 GUID= {317A1330-B07D-11E1-800C-444553540000} 297 ------------------------------------------------------------------- And then I started P3D again: NEXT: ===== [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Rudder Pedals 0.GUID={35A598E0-AAF5-11E1-8001-444553540000} 1=Saitek Pro Flight Yoke 1.GUID={35A598E0-AAF5-11E1-8002-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={7EC7D4F0-B1C3-11E1-8001-444553540000} 3=TQ6 3.GUID={317A1330-B07D-11E1-800C-444553540000} R=Saitek Pro Flight Rudder Pedals Y=Saitek Pro Flight Yoke T=Saitek Pro Flight Quadrant G=TQ6 265 ---------------------- Joystick Device Scan ----------------------- 265 Product= Saitek Pro Flight Rudder Pedals 265 Manufacturer= Saitek 265 Vendor=06A3, Product=0763 (Version 1.0) 265 Serial Number= 265 Found correct joystick Id 0 281 GUID= {35A598E0-AAF5-11E1-8001-444553540000} 281 Product= Saitek Pro Flight Yoke 281 Manufacturer= Saitek 281 Vendor=06A3, Product=0BAC (Version 3.2) 281 Serial Number= 281 Found correct joystick Id 1 281 GUID= {35A598E0-AAF5-11E1-8002-444553540000} 281 Product= Saitek Pro Flight Quadrant 296 Manufacturer= Saitek 296 Vendor=06A3, Product=0C2D (Version 2.0) 296 Serial Number= 296 Found correct joystick Id 2 296 GUID= {7EC7D4F0-B1C3-11E1-8001-444553540000} 296 Product= TQ6 296 Manufacturer= GoFlight 296 Vendor=09F3, Product=0200 (Version 2.0) 296 Serial Number= 00080 7 296 Found correct joystick Id 3 296 GUID= {317A1330-B07D-11E1-800C-444553540000} 296 ------------------------------------------------------------------- So at the first run it changed my numbers, but as I use JoyLetters this is no Problem. It fixed some registry Errors. In the next run the registry values are correct. So beside the changing of numbers no side effect. Hope this helps. Rgds Reinhard
  2. Hi, for the Feelthere E-Jets you have to work with mouse macros. Details about using mouse macros you will find in the "FSUIPC4 for Advanced Users.pdf" included in your FSUIPC Documents folder. The E-Jets don't use the standard FS controls. Rgds Reinhard
  3. Hi, Just to confirm: My good old LUA window showing VAS is now working again in QUIET mode since 4.962a. Thanks for fixing it. Rgds Reinhard
  4. Hi, I had the same problem. Since v4.962 with P3D 3.4 HF3 the VAS offset shows only 0. Also the maximun largest free block shows 0. Only the memory consumed by FSUIPC is shown correctly. I have set the OOMCheck to Quiet. I tried to monitor it in the FS title bar and on a WideFS client with a small LUA script, which I use since many months without change, Both variants always show 0. I tried to switch to Yes - and BINGO! Obviously the option "Quiet" makes a problem. Maybe it is also already in 4.61 as I copied the old DLL from a backup and experienced the same already with that version. But as I never did a flight with that version, I had not detected it until today. Rgds Reinhard
  5. Hi, According to AutoAssignLetters: The statement above is not completely correct: You should Keep it with "No" BUT you should assign letters in addition on your own. Here it is, how I have assigned my devices: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Yoke 0.GUID={35A598E0-AAF5-11E1-8002-444553540000} 1=TQ6 1.GUID={317A1330-B07D-11E1-800C-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={7EC7D4F0-B1C3-11E1-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={35A598E0-AAF5-11E1-8001-444553540000} R=Saitek Pro Flight Rudder Pedals Y=Saitek Pro Flight Yoke T=Saitek Pro Flight Quadrant G=TQ6 I assigned letters, which I can easily remember (like R for rudder). In my button and axis assignments I only use the letters: : 27=RY,2,C65607,0 -{ELEV_TRIM_DN}- 28=RY,3,C65615,0 -{ELEV_TRIM_UP}- : The Y in the RY assignment says, that the key 2 (repeated) on my Yoke should trim the elevator down. So even if numbers change (e.g. if you plug/unplug USB devices), the letters stay constant and therefore the assignments. Rgds Reinhard
  6. Hi, I have these two button assignments in my Q400 profile: 2=PY,22,CM2:2,100 -{Macro Q400LVAR: L:Q400_CONTROL_LOCK set}- 3=UY,22,CM2:2,0 -{Macro Q400LVAR: L:Q400_CONTROL_LOCK set}- So there is a LVar. Rgds Reinhard
  7. Pete, Obviously it was that little bit time needed, to broadcast the variables, as I defined the variables and started then immediately afterwards the modules relying on these variables. As I detected, that obviously the timing was my problem, I did the definition earlier in my start-up sequence, which resolved my problems. So I found a work-around. No need to change anything (never touch a running system) and with the new parameter everything can be controlled. My thread just should raise the awareness for other people, that global variables might be available later than before for other modules. Maybe this can be added to the ipc.set function in the LUA library document. Best regards and Merry Christmas Reinhard
  8. Pete, According to the release notes, you introduced with version 4.958 the possibility to share ipc.set global variables also over the network via WideFS. This is btw a great feature. I just want to inform, that by that obviously the time to set such variables might have changed. I have a lot of LUA modules communicating with GoFlight modules. As sometimes IDs and button numbers change, if you plug/unplug USB devices, I have defined them in one module globally by ipc.set() calls. In the several modules I then just use these variables. So should something change in button or module IDs, I just need to change it in one place. This worked now for several years. And suddenly I had problems with a few modules, not working as expected. The strange thing: which modules are not working, changed from flight to flight. No pattern. By debugging I found now out, that for one module not working the global variable for the buttons were not set, when I started the module. In my code I defined the global variables and then I started all my modules by ipc.runlua in the same script. And obviously the starting was quicker than the populating of this global variables (although everything was started out of one module). And all my modules are running on the flight sim PC (P3D v3.4, Win 7/64). I made the definition now earlier in my flow and at least at the last flights this seemed to correct the problem. I don't know, how the network replication could influence the timing, until the global variables are really visible to other modules. But maybe you have an idea. It's hard to reproduce and did not happen with all aircrafts. But especially with the Q400 from Majestic, where I have a lot of modules running, it happened most of the time. I have a work-around but it might also happen for other users. Rgds Reinhard
  9. Why are you using ipc.log if val == 1 ?!? Rgds Reinhard
  10. ... and btw: 4.957b is the current Version with a fix to 4.957c. You definitely should upgrade to the actual version, whenever you face a problem. BR Reinhard
  11. Chakko, Great work - nothing to add ;-) You found everything on your own. BR Reinhard
  12. Hi, For issue #2: The Pan command is a time-based command. So it pans not in defined steps but based on how long you are pressing the key. Even when you generate the key press by program, you experience differences in how far the pan moves the camera. You should look for FSUIPC offsets addressing the following Simconnect function: SimConnect_CameraSetRelative6DofByName This works better than panning. With that structure of offsets you are able to position single cameras/views exactly. In P3D v3 LM introduced obviously a small bug. But in FSX this should work. I don't know, if this works also in an WideView environment. But maybe this is a better alternative than just panning. Best regards Reinhard
  13. Hi, One short hint about the control assignments of FSX changing back to original state, when enabled. Try to set the configuration file read-only on Windows file base, when you have edited in the way you want it to be. This might help to avoid, that the standard settings come back. Not sure, if it works, but I always set the control configuration to read-only to avoid unwanted changes and never had any unwanted changes. Rgds Reinhard
  14. Hi, Have you already tried: x = ipc.readLvar("L:TURB ENG1 EPR") That's how I read Lvars (with success). Rgds Reinhard
  15. Hi, I have reported there too. I just wanted to cross-check here, if there might be something missing Piece in the implementation. Thanks for the quick clarification, Best regards Reinhard
  16. Pete, I switched to P3D 3.3.5 (by using FSUIPC 4.955) in the meanwhile. As P3D v3 is much smoother in terms of rendering, I changed my 3 screens for the outside view, where I had one large Eyefinity screen (combined via nVidia) to three seperate views (less distortion). So my views for the outside world are now named "3D view - View 01", "3D view - View 02", "3D view - View 03". Before I only had one view ("3D view 01"). I wanted to manipulate now this several views with this function. According to the P3D SDK, the function SimConnect_CameraSetRelative6DofByName should manipulate either cameras (and thereby all views) or single views: But it's only working for cameras (and there only for the first view). If I call the function with the name parameter "3D view", it works for the first screen and I can manipulate heading etc. If I use "3D view - View 01" etc. it doesn't give any reaction. I assigned different cameras to each of the three views and then I am able to manipulate each of them. So I have a workaround. My question is: I assume, you must be looking for the hSimConnect handle by some methods. Are looking for cameras as well as for views to get this handle, or maybe only for cameras? No idea, how this is done in SimConnect, but I assume, you know. As I said - I have a workaround. But maybe, when you have time, you may look again into that code. Best regards Reinhard
  17. Hi, There are special controls in the Advanced User Manual: 1054-1057 will increment/decrement the transponder digits. Check page 30-31 for them. Rgds Reinhard
  18. Hi, I did a first test. And voila: I had one error in my generic profile - one assignment, which should have been in an aircraft specific profile was created by me in the generic button section by error. Never detected that. But with the automatic documentation this is really easy to track down. Whenever we believe, that this product can't get better, it definitely gets better. Many thanks for that great new feature. Rgds Reinhard
  19. Pete, Often the simple solutions are the best. GREAT idea. This is the best way, to implement it. If it's implemented, I will be finally able to read these sections without always reading the manual in parallel. :D Best reagrds Reinhard
  20. Hi, It mainly depends on the condition, which you didn't specify, what to use. From my experience LUA is the most flexible way here. It will do, what you are expecting. And you can react on a lot of conditions. Rgds Reinhard
  21. Hi, See page 50 of the User manual - there you can synchronize the movement. Nice feature helping in such a case. Rgds Reinhard
  22. Hi, One small hint for you: You should switch from FSInn to vPilot for online flying on VATSIM. Much easier to configure, model matching is simple and it's maintained. Give it a try and you will be convinced. And the SB4 offsets are working ... Rgds Reinhard PS:Pete, I like the idea of a tool documenting the settings in a human readable way - would be VERY helpful
  23. Hi, The Dash Q400 is programmed in a way, that not the standard controls are used for these lights. You must create mouse macros and assign these macros to the buttons. As you typically have to click on several switches to turn all lights on, you might have to combine some of the mouse macros into a combined macro. This is documented in the Advanced User Guide of FSUIPC. Rgds Reinhard
  24. Hi, Anyhow you should try to set the second parameter in the [radios] section of your aircraft.cfg for ADF2 to 1. Because the second parameter typically defines, if there is a standby frequency available. This is only specified in the SDK for COM1 and COM2: "Two flags, set the first one to 1 if a Com1 radio is available, and the second if it supports a standby frequency." But I have seen this in other aircraft also set for ADF1 and ADF2. 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.