Pete Dowson

Surely with ProSim, it is ProSim's FDS driver which controls the device? FSUIPC wouldn't see it if so. I don't know FDS devices -- does Windows see the MIP as a joystick type device? Seems unlikely unless FDS supply a driver to emulate such. Questions about ProSim, which I think this boils down to, are best dealt with on ProSim's own forum. Pete

Prosim has a facility to log inputs it detects. FSUIPC has a lot of logging facilities. But you need to be specific on "the things" which you think are supposed to talk between Prosim/FSUIIPC/Prepar3D. Most of the 737 controls are operated by Prosim -- it simulates the entire cockpit, and all of your controls and switches need to be assigned (and calibrated) in Prosim. PMDG's aircraft have their own cockpit. You use Prosim OR PMDG. You can't use one with the other. That would make no sense. I think you need to be using the Prosim support forum to resolve any problems you have with Prosim. FSUIPC really has little to do with it unless you are setting Prosim into FSUIPC mode -- you should start off using it's SimConnect mode in any case. AND the aircraft model supplied with Prosim, of course. Pete

Controls for Prosim need to be assigned in Prosim. As your FSUIPC is unregistered it is not even looking at the controls. In fact it is doing little except supporting requests from other programs, including Prosim if so configured. You really need Prosim set to SimConnect mode, not FSUIPC mode, unless you plan to purchase FSUIPC and register it. Pete

Here's a version of MakeRunways for testing (5.132). It ignores airport records with an ICAO Id or more than 4 characters. For each one so ignored a message will be seen in the Log ("Runways.txt"). Please try it and let us know. Perhaps you can ZIP up the log (Runways.txt) and send it for me to check. If even the Zipped file is too big, maybe at least show portions flagging ignored entries or any problems you see. Thanks, Pete MakeRwysTEST_5132.zip

I think the problem arises because CAD54 is not a valid ICAO ID. The ICAO system of IDs only allows 4 characters. It looks like MakeRunways is only comparing with the first 4 characters, CAD5. When I get the time I'll have a look to see how easy it is to program around. I'll probably simply ignore (bypass) all entries with more than 4 character IDs. I don't know if this will eliminate anything significant -- perhaps you can tell me? I fear the changes which would be needed to deal with >4 character IDs 'properly' would be more work, and more complicated, than I am willing to tackle. Pete

Take a look at the log ("Runways.txt"). That shows everything it did (and tried to do). You should download the latest Makerunways release too -- yours appears to date beck to 2017! Except with MSFS you should run MakeRwys in the main FS root folder -- the one with the sim's EXE file. And you need the Lorby export program there too -- it is included in the downloadable ZIP. The "scenery.cfg" file is obtained from where it is maintained by FS, and the Lorby program adds whever might be added in Add-on files. Pete

I assume so. If you look at the Deletion lines in the MakeRwys log file (Runwats.txt) if think that's the only likely one. Pete

Prosim supplies their own 737 model. It isn't compatible with others. This is nothing to do with FSUIPC -- you evidently have scenery and aircraft conflicts. Use the Prosim aircraft with Prosim. Try to fix your scenery by eliminating each of your add-ons one by one till you find the culprits. Please also note that FSUIPC3 is no longer supported -- for a long time now! Maybe your Prosim is too, out of support. Pete

You don't. With Prosim you should assign all axes in Prosim itself. Probably this wasn't so important in Version 1 of Prosim -- I don't remember, it was so long ago (it has developed apace since then) -- so if you want to assign in FSUIPC then both Captain and FO toe brakes are assigned to the same single toe brake axis. Same with all the other flight controls. For proper advice on configuring Prosim, whether via FSUIPC or not, you should us the Prosim forums. Pete

You are the only user so far with such a problem. Evidently something went wrong during MSFS's original installation, as it should find it no matter whether it is in Admin or not. Are you running it "as administrator", as instructed? MakeRwys finds MSFS by looking for "UserCfg.opt", which should be in one of these places: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache or (for the Steam version): %APPDATA%\Microsoft Flight Simulator". so your %APPDATA% system variable appears to be C:\Users\Admin\AppData\Roaming. Try entering %APPDATA% is the Start search entry and see where it takes you. Mine takes me to C:\Users\Pete\AppData\Roaming. If yours doesn't take you to the correct place then something is screwed up in Windows. Development of MakeRunways has long terminated, and the program source made available for any programmer wishing to take it up. I am retired and I now have no way to delve into what could be going wrong for you. I can only offer two ideas: 1. Uninstall MSFS and re-install it. But first: 2. Try placing MakeRwys.exe into whichever of those places where UserCfg.opt is placed, and run it with /LOCAL as a parameter, in Admin mode of course. Pete

ICAO codes are 4 characters. The airport indices I have don't even have any starting BW yet alone BW314. Seems like a fictional airport (?), but they should still keep to 4 characters. Most software, including everything likely to use MakeRwys data, will only deal with 4 characters. Note that, in any case, the BGL format allows one DWORD (4 bytes) only for the ICAO ident. -- see for instance Page 8 in the FSDeveloper Wiki for MSFS BGL formats. BGL File Format - FSDeveloper Wiki.pdf Pete

No one else so far. There are no changes in the BGL layouts and format between 5.4 and previous versions. I am using it on 5.4 with no problems, so it sounds like a corruption in the scenery installation. But you are using an older version of MakeRunways (4.90). The latest is 5.13, so please try that first -- download it from FSUIPC.com, or from the Download Links subforum above. I need to see this file to help further: E:\Lockheed Martin\Prepar3D v5\MakeRwys_Scenery.cfg Pete

So, what did you change in between? We need to see the log -- the "Runways.txt" file in the MakeRwys folder. That will likely show the reason. Pete

No, they aren't related to the radar image. As I have said several times, the Radar.bin file is just an array of cloud vapour density values. These other values are just made available via FSUIPC's offset memory. As I said elsewhere, the radar data is provided by a Call Back for the DLL, set by a parameter for the SetRdrarams function, which has this definition: void (*pSetRdrParams)(long aircraftHeading, long range1, float tilt1, long range2, float tilt2, RadarDataComplete callBack, void *pContext, long optionsFlag) = 0; The CallBack function is defined like this: typedef void (CALLBACK *RadarDataComplete)(long rdrSmallDimSize, void* rdrData, void* pContext); However, the Active Sky DLL is meant to be run inside P3D (like FSUIPC). I wouldn't have thought it worked outside. But surely you should have all the information you need in any case -- didn't you say you had the AS API? Pete