
John Dowson
Members-
Posts
13,284 -
Joined
-
Last visited
-
Days Won
271
Everything posted by John Dowson
-
Then you need to load the AS_connect dll, get the addresses of the functions/variables you want to use, and then use them to generate the radar/bin file: ... if (!hBtstrpDLL) hBtstrpDLL = LoadLibrary("as_connect_v5.dll"); if (!hBtstrpDLL) hBtstrpDLL = LoadLibrary("as_connect_64.dll"); if (!hBtstrpDLL) hBtstrpDLL = LoadLibrary("as_connect_v6.dll"); if (hBtstrpDLL) { // Get pointer to its exported "ASN running" BOOL BYTE *(FSAPI *ASNIsRunning)(void) = (BYTE *(FSAPI *)(void))GetProcAddress(hBtstrpDLL, "isActive"); if (ASNIsRunning) ... pAmbientIcing = (BYTE *) GetProcAddress(hBtstrpDLL, "AmbientIcing"); pWshLat = (float *) GetProcAddress(hBtstrpDLL, "WshLat"); pWshLon = (float *) GetProcAddress(hBtstrpDLL, "WshLon"); pWshRange = (float *) GetProcAddress(hBtstrpDLL, "WshRange"); pWshMinAlt = (float *) GetProcAddress(hBtstrpDLL, "WshMinAlt"); pWshMaxAlt = (float *) GetProcAddress(hBtstrpDLL, "WshMaxAlt"); *((FARPROC *) &pSetRdrParams) = GetProcAddress(hBtstrpDLL, "SetRdrParams"); pAmbientTurbulence = (float *)GetProcAddress(hBtstrpDLL, "AmbientTurbulence"); pExportedPrecipType = (BYTE *)GetProcAddress(hBtstrpDLL, "ExportedPrecipType"); pExportedPrecipRate = (BYTE *)GetProcAddress(hBtstrpDLL, "ExportedPrecipRate"); pExportedAmbientVisibility = (float *)GetProcAddress(hBtstrpDLL, "ExportedAmbientVisibility"); pInCloud = (BYTE *)GetProcAddress(hBtstrpDLL, "InCloud"); ... Exact details on how to use the dll functions should be provided/available from ActiveSky. John
-
I am slightly confused by this as there is no Active Sky for MSFS - as far as I am aware... This makes sense, as there is no radar data (bin or jpg) produced by FSUIPC7, as there is no ActivceSky for MSFS. And is this radar image correct? Does the data/image come from ASN or MSFS? There is no way to get weather radar data via simconnect. There is a WebAssemply API that is provided that allows weather data radar images to be created and used in glass cockpits - the MapView API - maybe ProSim is using this? See https://docs.flightsimulator.com/html/Programming_Tools/WASM/MapView_API/MapView_API.htm I did look into this API to see if it could be used to generate a radar weather jpg (but not a radar.bin file - that is ASN specific) via the FSUIPC WASM, but it was not obvious that this could be done easily as the API looks more like like something to be used by aircraft developers. I may spend more time looking into this API to see if it can be used by FSUIPC at some point in the future. John
-
Sort of...FSUIPC see's a press on the first button press and a release on the second (or vice-versa, depending on the initial state of the button's toggle flag. The button assignment panel only registers a button when it sees the press, not the release, although you can assign to the release in the same panel. Yes, you should be able to do that - as I suggested earlier, you could try using the beacon/nav lights on preset on the press, and the off preset on release (or vice-versa). Note that you can simulate this type of action on any button by using the buttons' latch flag, denoted by an F when using compound button conditions - see the Advanced User guide for details. Not good memory, unfortunately - I just searched these forums for a similar issue. Try the forum search in future, rather than just google. Cheers, John
-
You didn't really answer my questions...can I assume then that its the second case, and that the first button press is not detected/logged? This would also imply that the first press isn't being detected for some reason. This issue has also been reported previously - see So it seems that this is how the VRI MCP works, as a (sort-of) toggle - so on one press you get a press event, and the next you will get a release event. And as you assigned only to the press event, its only taking action every other press. So the solution would be to assign the toggle preset to both the button press and release. Also see the following topic conversation that talks about this issue: John
-
But do you see the first press registered/logged/detected by FSUIPC? Your log shows two button presses for the beacon lights (with another two a short time later): If you see the press being detected and logged each time, and the preset is being executed, it can only be a problem with the preset calculator code. Which version of the FBW A320 are you using (release, dev or experimental)? Have you tried switching to using the on/off presets on press/release instead? If you don't see the first press detected/logged, then the issue will be with the lua that is being used for your VRI device. As it looks like you are using LINDA for this, you should contact LINDA support if that is the issue. John
-
C172 Master and Avionics Switches macros
John Dowson replied to raynald1's topic in FSUIPC Support Pete Dowson Modules
You can do this with an "offset condition" - see page 24 of the Advanced User guide, section ADDING OFFSET CONDITIONS. You need to have an offset that holds the current switch position, then you can add a test on this value to determine if the assignment should be triggered or not, depending upon what value the offset holds. Try adding this yourself - if you need further assistance then please show me/attach your FSUIPC6.ini file. -
MakeRwys in MSFS & Airline gate assignments
John Dowson replied to Fiorentoni's topic in FSUIPC Support Pete Dowson Modules
As it says on the download page (on SimFlight) for MakeRunways: Looks like I still need to update fsuipc.com with this information though... John -
No, but you MUST understand how these things work. When using a profile, if an axis or calibration section is present in the profile, then these profile-specific section will be used and the general axis and calibration sections will be ignored completely. However, if either of these sections is missing from the profile, then the general sections will be used. Button and key assignments work in a different way. All general button and key assignments are inherited in a profile, unless overridden/redefined. That really shouldn't happen - only the ATR profile assignments should be used as they will replace the general assignments. If you think that this is not the case, then you need to show me/attach your complete FSUIPC7.ini and ATR.ini profile files, and also a log generated with logging for Buttons & Keys and Events activated. This will show what assignments are being selected when you press the button/key.
- 1 reply
-
- 1
-
-
Strange Errors in FSUIPC Log
John Dowson replied to Jackson5's topic in FSUIPC Support Pete Dowson Modules
Such errors can sometimes be safely ignored, especially if they are only reported in a single add-on aircraft. But if they are reported for many aircraft then this can be a sign of corruption in your P3D installation, and you should re-install the P3D Client component. John -
You can use the control number of the Offset Byte control that you want to use to write to offset 0x0B46, with the appropriate parameter - see the Advanced User Guide on page 33. Otherwise, if there is a custom control number for the aircraft you are using, yo can also use that. Or if there is a preset available, yo can calculate the control number of the preset and use that, although it is better to use the preset name itself via offset 0x7C50. John
-
Spoiler Axis for FSLABS A320x
John Dowson replied to Vincent Guerandel's topic in FSUIPC Support Pete Dowson Modules
That is correct - there is no specific functionality for speedbrake detents. How have you assigned your speedbrake axis? You could try assigning in the right hand said if the axis assignment panel, where you can set a specific value for the speedbrake when entering/leaving specific ranges. This should allow you to set the specific value for a detent when entering the axis range around that detent.- 1 reply
-
- prepar3d v5
- fsuipc6
- (and 3 more)
-
Windows 10 and FSUIPC v4.977
John Dowson replied to Reco's topic in FSUIPC Support Pete Dowson Modules
Ok, thanks for the update. John -
Windows 10 and FSUIPC v4.977
John Dowson replied to Reco's topic in FSUIPC Support Pete Dowson Modules
Sorry, but I don't know what else to advise. You can check the windows Event viewer to see if anything is reported there. You can also check that your VC++ redistrubutables are up to date - but I have never seen an issue with the VC++ redistributables with FSUIPC4 before.... There is nothing wrong with the installer - it has been downloaded and used by thousands of people without issue. The issue is certainly specific to your system and I cannot advise any further on this. If all else fails, you can try manually installing FSUIPC4. To do this, create a Modules folder under your FSX folder and place the FSUIPC4.dll in it. You then need to manually modify the FSX dll.xml file, located under <your user account>\AppData\Roaming\Microsoft\FSX If the dll.xml file doesn't exist, you can create it with the following content: If it exists, just add the FSUIPC4 <Launch.Addon> section John FSUIPC4.dll -
I do not understand what your issues is.... your GoFlight modules should be detected and available for assignment just as any other controllers. In your FSUIPC7.log file you should see the devices detected - this is what mine shows: If you then go into FSUIPC's button assignment panel, you should see the button presses detected and can be assigned there. John
-
FSUIPC and PF3 Not Communicating
John Dowson replied to theguard67's topic in FSUIPC Support Pete Dowson Modules
Also, check that you are running everything at the same privilege level - if one application is running with administrator privileges, then everything else must be ran at the same privilege level or they won't connect. -
FSUIPC and PF3 Not Communicating
John Dowson replied to theguard67's topic in FSUIPC Support Pete Dowson Modules
Your log shows no issues. I can's see how this can be an FSUIPC issue, but you can try setting logging for IPC Reads and IPC Writes - this should then log any activity of programs that use FSUIPC. -
Windows 10 and FSUIPC v4.977
John Dowson replied to Reco's topic in FSUIPC Support Pete Dowson Modules
When you run the installer, the first thing that should happen is that windows should show a 'User Account Control' window that ask you to grant permission for it to modify your system. Check your task bar to see if that window is iconised for some reason. You can also try right-clicking and 'Run as administrator'. -
No - you shouldn't need that.
-
Download an install (copy to your FSUIPC7 installation folder) the 64-bit GoFlight drivers from fsuipc.com.
-
Just download and run the installer. You can select where to install FSUIPC7 - you can install it anywhere you like, but you should not install it in a windows protected folder, such as under Documents or Program Files. There is no need to install or copy any dlls, unless you have GoFlight or PFC devices that require the drivers I provide. As for how to use, you need to refer to the manuals provided. I can help with specific issues, but you need to consult the manuals for an overview. Unfortunately they are only available in English for FSUIPC7. There are some manuals available in French for FSUIPC4 - most of this will still apply, but there are many new facilities relating to the use of the lvars/ hvars and presets/calculator code (via the FSUIPC WASM module) that are only documented un the FSUIPC7 manuals. John
-
Ok - if using reverse on the axis range, you have to configure idle to be at around -8000 in the EFB throttle config, and then you get reverse thrust in the -8000 - -16384 range.
-
First, there are now quite a few (423) MF presets available for the ATRs. These are relatively new and are not available in the events.txt file that comes with the latest version of FSUIPC7. The latest file that includes these events is attached - you can use it to replace the one in your FSUIPC7 installation folder: events.txt (The ATR presets start with MSATR) For the throttle configuration, this depends on whether you want a reverse axis on the throttle axis or not. If you want a reverse axis, then just assign your throttle axis/axes to Throttle 1/2 Axis Set Ex1. If you have a reverse axis configured in the EFB, then this will give you the full range of the throttle movement, including reverse. If you don't want to use the reverse range of the axis, simply go into the EFB and deselect/uncheck the Throttle Hardware has reverse axis option. This will then give you the range between F1/G1 (depending on state of Idle Gate) and full power (i.e. no reverse). You can also use a preset to control the throttle and limit its range (i.e. no reverse) without going into the EFB to uncheck for reverse thrust. This will depend on your throttle axis range, but for a standard range of -16384 - +16384, then the following preset (added to the myevents.txt file) will give the range between F1/G1 (depending on state of Idle Gate) and full power, even when the EFB throttle config is set to use a reverse axis: MSATR THROTTLE1 LEVER SET2#@ 16384 + 0.74414 * 8000 - -8000 max 16383 min (>K:THROTTLE1_AXIS_SET_EX1) MSATR THROTTLE2 LEVER SET2#@ 16384 + 0.74414 * 8000 - -8000 max 16383 min (>K:THROTTLE2_AXIS_SET_EX1) (what this does is add 16384 to your axis value to give a range between 0 - +32768, then scales this to give a range 0 - +24384, then subtracts 8000 to give the axis range as -8000 - +16384, idle to full) To assign to these presets, once added to the myevents.txt file, check Select for preset and assign to the preset on the axis in the left-hand side of the panel, as you would to any other axis control. However, I do think it is (probably) better to just assign to Throttle 1/2 Axis Set Ex1 and then calibrate in the EFB, either with or without the reverse thrust. NB I'm not sure how to get into reverse thrust yet even when using the axis - it doesn't seem to go into revere even when full reverse set on the lever (I am probably missing something here...). Therefore probably better to use the no reverse thrust EFB config option for the time being. I will look into reverse thrust config another day, but If anyone has reverse thrust working, on an axis or otherwise, please let me know how this is configured on the ATR... I also find it useful to set a switch (or button) for the throttle idle guard, using the presets MSATR_ENG_IDLE_GATE_FLT_PUSH (on press and MSATR_ENG_IDLE_GATE_GND_PULL (on release) - note that MSATR_ENG_IDLE_GATE_TOGGLE is also available. For the condition levers, you can use the following presets (again, add to your myevents.txt file): MSATR CONDITION1 LEVER SET2#@ 16384 + 10923 / near 0 max 3 min (>L:MSATR_CONDITION1_POS) MSATR CONDITION2 LEVER SET2#@ 16384 + 10923 / near 0 max 3 min (>L:MSATR_CONDITION2_POS) If you assign an axis to those presets, this will give you the 4 discrete positions (0-3) over the full range (-16384 - + 16384) of the axis. Also make sure that you do not calibrate the throttle axis in FSUIPC - make sure that you have a profile-specific calibration section, and reset the calibration for the throttle on pages 1 and 3. John [N.B. I have added a '2' to the preset names to distinguish them from the MF presets, which are documented on the HubHop site but don't appear yet in the events.txt file]
-
LUA script for approach callouts
John Dowson replied to alder's topic in FSUIPC Support Pete Dowson Modules
Why don't you try looking at this yourself? Keep a backup/safe copy of the working script, and then try removing/commenting out (using '--') the functionality that you don't want to use...