Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    12,268
  • Joined

  • Last visited

  • Days Won

    250

Everything posted by John Dowson

  1. The ASNwxRadarPath parameter should be the complete path to the file. Does the folder 'Sim-Avionics' exist? To test. just try ASNwxRadarPath=c:\radar.bin
  2. There's the offset status spreadsheet, included in the downloadable zip file. Currently at version 11. The controls list is generated at runtime and will be in your FSUIPC7 Documents folder. However, this is just a list and many are not currently working, and some work in some aircraft but not in others.
  3. When you turn your rotary, what do you see in the Button & Switch assignment panel? You should see the 'Joy#' letter, which is the letter that is assigned to your device, and a 'Btn#', which will change when you turn the rotary switch. The example I gave was for when the rotary is linked to buttons 17 and 18. To program the rotary correctly, you need to determine what button numbers your rotary is using, and when/if it is sending the press & release events. To check this, you can activate logging for 'Buttons & Keys'.
  4. The .bat file just contains a html page with an embedded javascript section which I guess is the problem. Not sure why Kaspersky (and also Malwarebytes flags this as a virus. Other virus scanners seem to be ok, although I have had one report of Windows Defender marking it as suspicious, which is strange... I'm not sure there's anything I can do about this, you just need to add an exception or restore it once quarantined, however the virus checker works. I don't have or use Kaspersky, so I can't really advise. John
  5. @Don777 You are quoting a post over 15 years old! And if its a direct question to a previous posted, a good idea to tag them which gives it a better chance of being seen. But your answer should be in this post...did you try?
  6. You could try offset 0x0B49 instead - Autopilot Flight Level Change. See the following previous posts which may be relevant:
  7. Btw, have you tried writing to this offset? If so, does that change the A/S hold state?
  8. Ok. So it reads 0 when A/S hold is active? how about 07E2, is that correctly populated with the speed set? How about the other A/P Hold/lock variables/offsets? There are various known issues with the G1000, with various key events having no affect and simvars not being populated correctly. I'll take a look at this in more detail, but I suspect that it is another G1000/SDK issue.
  9. I've checked this now and FSUIPC7 is requesting this data, but it seems that the following AI string variables received via simconnect are always empty: AI Traffic State AI Traffic Assigned Runway Ai Traffic FromAirport AI Traffic ToAirport AI TRAFFIC ASSIGNED PARKING I will raise this with Asobo. I'm not sure at the moment why TrafficLook is showing an integer in the 'To' column when this should be empty.... John
  10. Which aircraft/autopilot are you using? You really need to specify the aircraft for all queries on offsets or controls.
  11. What controls are you using, and how does your 3-point switch function? In the C172, you should the control Fuel Selector Set, with a parameter if 1 for center, 2 for left and 3 for right. And how you assign depends on the button/release events that your 3-point switch uses. For example, I have a 3 point switch that when moving from center to up, triggers a button 17 press, from up to center, a button 17 release, from center to down, a button 18 press, and from down to center, a button 18 release. To use this for the fuel selector switch, I would assign a Fuel Selector Set with parameter 3 on button 17 press and a parameter of 1 on 17 release, and a parameter of 3 on button 18 press and again a parameter of 1 on release.
  12. Yes. The latter - create the text file, addthe content and rename it with a .reg extension.
  13. You can use the default hot key (Alt-F) to display the main window, double click the FSUIPC7 icon (in your system tray), or right-click the icon to select the required function. Please see the provided documentation - as well as the Installation and Registration guide + README.txt available in the zip file you downloaded, the main FSUIPC7 documents are installed under your Documents folder in an FSUIPC7 sub-folder.
  14. Do you know when this occurs? Can you provide steps to reproduce? I have been using FSUIPC7 on a multi-monitor set-up (3 monitors) with FSUIPC7 positioned on different monitors and I haven't noticed it losing the monitor or correct position so far. Are you maybe using nvidia surround configuration? Are your monitor ids changing? If you can let me know how I can reproduce I'll look into it.
  15. Ok, thanks for reporting back.
  16. @pilotjohn Rather than confusing the button/key definition with adding syntax for a delay, I've decided to add a pause control (C1152). You can use this to add a delay either before or after a keypress or button assignment, by overloading the assignment. Here's an example of inserting a delay between two controls being sent (to control the 3-way off->Taxi->LNG lights toggle in the TBM930): The parameter to the control is the delay in milliseconds (600ms in the above example). (NB. there is minor issue in that the FSUIPC added controls are currently not annotated/commented correctly) This added control is available in version 7.0.2a attached below. Cheers, John FSUIPC7.exe
  17. I have added a pause control now, so you can add the pause in the assignments if you like rather than using the lua. These assignments would do the same as the lua (update index numbers accordingly): Of course, you can continue using the lua, but the pause control will be available if you need it for anything similar in the future. Its in the following version, and will be released officially when I release 7.0.2: FSUIPC7.exe
  18. I'm not familiar with that device, so not sure how the "throttle cursor" is seen by FSUIPC. If its an axis, you can assign to the left/right brake axis and calibrate. If its a button, then you could look into using the lua posted here:
  19. Hi, I presume that you are talking about mouse macros. I'm not sure why this would reduce your FPS so much. Does it return to normal once you have finished creating the mouse macro? Can you still create the mouse macro? I don't have any fslabs aircraft, but I think there are quite a few people who are using FSUIPC6 with them. You may be better off asking over on the FSLabs forums. There's also a good guide to using FSUIPC with the FSL A3xx aircraft on their forums: https://forums.flightsimlabs.com/index.php?/topic/22402-v440-update-in-depth-tutorial-to-bind-switches-and-push-buttons-to-keyboard-or-hardware-for-the-a3xx/
  20. The usual way to find out if there are any controls/events assignable is to activate logging of non-axis events. You can then see what events are being used when you activate the UI control, and use the same event when you program your button or switch. However, there are currently many reasons why this may not work: - some functions may be performed internally by the guage software. If this is the case, you won't see any events. In previous FS versions, such functionality could be handled by using lvars (local variables), if provided. Currently in MSFS/FSUIPC7 there is no access to such variables - some events that are triggered by activating controls in the UI have no affect when sending them via SimConnect. This is a known issue for many events (e.g. view and slew controls) - some controls work in some aircraft but not others. The airliners seem to suffer from this the most, especially the A320Neo. This is probably due to the fact that they model more of the systems than relying on the internal models. There are various tricks, tips and mods around, especially for the A320Neo it seems. Try searching the forums (here and the msfs/asobo ones). Duplicating mouse wheel operations (to program functions not available via SimConnect or using lvars) was a feature of previous versions of FSUIPC (i.e. in v4, 5 and 6). However, the functionality to implement this is currently not available in the MSFS SDK. We will look into adding this back once the functionality is available in the SDK. Please remember that even though MSFS is now released, the SimConnect SDK (which is what third party products rely on to communicate to the FS) is still at version 0.7.1. Things should improve as the SDK develops. John
  21. With auto-connect disabled, it will only connect when you tell it to. You can only connect once FSUIPC7 has detected MSFS is running, and you can connect as soon as MSFS' SimConnect interface is ready, which occurs sometime during loading. However, if connecting manually, best to do it once MSFS has loaded and is on the home screen. You don't have to have an aircraft loaded, although other things (e.g. WideServer, luas, etc) won't be started until an aircraft is loaded.
  22. Just checked this in P3Dv4/5 and FSUIPC5/6. Its the same problem there, but as FSUIPC5/6 is a dll rathe rthan a separate application, the controller works when P3D has the focus but not when other applications have the focus. As I said, I will look into this but it may take a while.
  23. Sorry, that is only for the polling of your button assignments. In the HidDemo.luia, adjust the Pollrate variable instead.
  24. Hi Nigel, ok, I can see the issue. With my xbox game controller, connecting via bluetooth its reported as: whereas cabled: However, in both cases it suffers from the problem that FSUIPC7 only recognises inputs from this device when FSUIPC7 has the focus. I'll look into it and get back to you, although this may take a while. I'll also talk to Oliver/Lorby. Thanks for reporting this, regards, John
  25. Not sure. You could try looking at the Rotaries.lua example to see if that helps. You could also try adjusting the PollInterval in your [Buttons] section of your ini.
×
×
  • 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.