Pete Dowson

Sorry, do you mean that you assigned some keypresses but forgot what you assigned them to? If so, then they should have descriptive labels in your INI file, and also you can review all assigned keypresses on the right-hand side of the Keys assignment tab in the FSUIPC options. Or do you mean they've appeared out of the blue, none of your doing, or copied from someboday else? Ah, you supplied your FSUIPC4.INI file. Let's see ... This shows two things: 1. You are using an old and unsupported version of FSUIPC. The current version is 4.974 (you are using 4.929c). Please update NOW, before returning for more help. 2. The INI file you have provided shows absolutely no Keypress assignments -- so why do you think you have some you don't know the purpose of? If you have Wideclient running on COMP2 then it will send any button presses on a recognised Joystick device 9recognised by Windows) to FSUIPC automatically. You then assign them in the Buttons & Switches tab. This is nothing to do with keypress assignments. Looking at your Button assignments you already have 24 button assignments all from two separate WideClient computers -- KURT - INSTRUMENT and INST - 3. they are all related to operations on FSUIPC Offsets. With the current version of FSUIPC, such entries in the INI would be annotated. UPDATE! Pete

You didn't need to post a picture, just copy (select and copy, as in copy and paste) the "Target" field. What is the actual entry you have in the Run parameter. In your original message here you said "starter.exe /starterengrun.exe", but that Properties entry only has "starter.exe"., so you aren't doing the same thing in FSUIPC. And you never mentioned an error message. Is it from that program? What does it say? Can you ask the support for the program (JeeHell?) what might be going on? Could it be related to privilege levels? i.e. is it marked to "run as administrator"? Because if so, and it needs that, then for FSUIPC to run it the same P3D/FSX would have to be run "as administrator". Pete

Unfortunately, the RUNWAYS.TXT file you attached is incomplete. It only shows up to Layer 004 (Orbx Vector). So it isn't reaching any real airport scenery. It is only 1Mb long. On my test PC I have a lot less scenery than you (just defaults + 4 add-on layers) and mine is over 100 Mb. So please ZIP up the complete file (which will make it small enough) and attach that instead. If it is happening on the very last entry then it sounds as if it occurs AFTER it has built all its tables, but before it manages to produce of complete the many files it makes. So, are there any part-written files? It makes these if it can: f4.csv, f5.csv, g5.csv, helipads.csv, r4.csv, r5.bin, r5.csv, runways.xml, t5.bin, t5.csv, airports.fsm, FstarRC.rws, runways.csv. Aso, what does the progress window actually show at the time, it hangs? If none of the files are produced, I'm wondering if it hangs when it tries to sort things. I suppose there's a possibility that it is running out of memory, but that seems unlikely. I know it is only a 32-bit program, not 64-bit, but there should easily be enough. And my cockpit PC has a CFG file with 393 layers and there are no problems there. Was it a previous version but with the same scenery, or different (less?) scenery and this current version? How long ago is "used to"? Pete

It's very strange that no scenery file is listed. The normal format is like this example ============================================================================= Area.003 "0000 Base" (Layer=3) Path(Local/Remote)=Scenery\0000 ============================================================================= Scenery\0000\scenery\APX03070.bgl ============================================================================= It isn't actually reading ay data as suchuntil it gets to the BGL file. What BGLs are there in EnvTex? Could you show me the folder contents please? It's the actual file i need to see what could possible generate a crash. I also need the precise version number of the MakeRunways program you are using. (Right-click, Properties). Pete

It can help you do it. To transmit to the Arduino would require a Lua plug-in which you'd need to write. The joystick would then be assigned to send the axis values to this plug-in. The plug-in should be preloaded and set to wait for axis values as events. The events would be changes in the main Parameter which is sent by assignment in FSUIPC axis assignments to the LuaValue control. You'd need a registered (i.e. paid for) FSUIPC. Take a look at the documentation, expecially for the Lua features and the examples provided. We can help in more detail when you'd done so. Pete

You musr place MakeRunwys into the main P3D folder and run it from there. That's where all its files are produced. The only one made ititially will be "RUNWYS.TXT" which is a full log of all it does, including what files it is reading. If it isn't there you have never run MakeRunway with that install of P3D. Maybe you have Windows hiding file types from you? If so it will simply list as "Runways" and be described, probably, as a text file. Pete

Calibrated in FSUIPC? Are you using FSUIPC for any controllers at all? If not, what you see in the Calibration tab is what is arriving in P3D. So something is sending those. I do not want to see videos. If you are not assigning in FSUIPC, and you are not calibrating in FSUIPC, then FSUIPC has no part in any of this. Maybe you have Prosim sending controls to P3D and also have controllers enabled in P3D. Yo must use one source -- FSUIPC assignment, ProSim assignmnet, or P3D. Otherwise yo will get conflicts. I thought that the recent versions of ProSim demanded that the main flight controls were assigned there? But I'm pleased nonetheless that this isn't really an FSUIPC support question at all! Don't delete things there. Just disable controllers. Otherwise when P3D sees what it may think are new attachments it will automatically make assignments. ALWAYS use the disable controllers option instead. There's no need to delete assignments. Pete

What does it show in the axis assignment tab. That's more to the point as it is showing only and exactly what it is reading from the device. The calibration screen could be getting values from somewhere else, a duplicate assignment of controllers left enabled in P3D. Under oars? Sorry, please clarify this! Pete

I'd need to see the log file 9Runways.txt), or at least a good section before it hung. I used to use EnvTex till recently and I don't think I ever saw it create a scenery layer. Is this some updated version which tried to do that rather than replace the default textures? Pete

I've no idea how it knew what town or city was nearby. Airports, yes, that's an existing data base which can be generated and referenced. But i don't know of any easily accessible digital gazeteer with Lat/Lon coordinates which could be searched. Pete

If you make a desktop shortcut for it, what does it look like? (Right-click - Properties - Link). Pete

You can have Ctrl+null if you edit the INI file assignment, In FSUIPC do something like Ctrl+A. Then look for the assignment with 65 as the key (65 = 'A') and changed the 65 to 0. It would be possible on the keyboard but there's no "null" key! 😉 Pete

The function is part of SimConnect, so you need to report this on the L-M forum. Pete

Yes, good. but does it have the same affect as using the Autosave facility? That was the intent of my question. I was trying to determine if it is specifically a Simconnect problem, or a Save action problem. Pete

Did you try using the Menu save flight option, or the ; key (if that is still the defined short-cut)? Pete

Thanks for pointing it out. Very annoying blaming FSUIPC then closing the thread. I posted a new topic as follows [NOT RESOLVED] View Group Managment - FSUIPC The above thread (without the "NOT") has been closed as "RESOLVED". The resolution appears to be: Now this still points to a problem in P3D. All the FSUIPC AutoSave does is generate a filename and call the SimConnect function to Save a flight. It is actually identical to the user pressing the ; key to save a flight and entering his own name when prompted. The difference is only that it saves the bother of entering the name, and saves automatically at regular specified intervals. Of course, saving a flight is often also detected by add-on aircraft code and used to trigger them to save aircraft configurations too. So it could be an aircraft add-on rather than P3D specifically. It still needs investigating though, rather than wrongly blamed on FSUIPC and thread closed! Pete

Not "offset" (those were used in mouse macros for FSX and P3D1-3 panels) but "mouse rectangle ID". Different views (virtual cockpit vs standard 2D cockpit, different gauge sets like overhead, pedestal, etc) will all have different sets of mouse rectangle IDs, but they certainly should not change for the specific gauges of the same type (VC or 2D) and the same view. Have you tested with other aircraft? I only have default ones apart from my Prosim737 which has no panel in any case. If it is only the Blackbox A330 you might like to check their support or ask them more directly what might be going on. Possibly it's related to the way that is programmed or initialises itself. It's then really their job to get it working according to L-M rules -- either that or report the problem to L-M. If it affects even default aircraft, or all add-ons, on your system, then there is certainly something specifically wrong on your install. You'd need to report that to L-M with full details of your system and add-ons being used. Pete

I have been doing lots of tests, making macros for default aircraft. I'm gone back and forth between P3D4.5 and 4.4 (but not changing the Content, only the Client. I have no add-on aircraft except the Prosim737 and that has no pabels in any case, so I based my testing on the Beech King Air 350. In P3D4.5 i made this macro file: [Macros] 1=AltAlert=RX1000,3 2=BARO-=RX800,3 3=BARO+=RX801,3 4=WARNING=RXe800,3 5=CAUTION=RXe000,3 6=AP=RX1d800,3 7=FD=RX1d804,3 8=HDG=RX1d801,3 9=ALT=RX1d805,3 10=NAV=RX1d802,3 11=B/C=RX1d806,3 12=APPR=RX1d803,3 13=YD=RX1d807,3 I then loaded other aircraft and viewed their panels, and went back to the same King Air 350 and made the same set of macros again -- with exactly the same results. I closed P3D4.4 down, the reloaded it, loaded some other aircraft then the same King Air, and made yet another macro file -- again, results identical. So then I uninstalled the 4.5 client and installed the 4.4 one. Went through the same process there, and every time i got the identical results. So, my conclusion is that the facility works, that the rectangle IDs remain the same (as they should do since this was fixed in 4.4). Note however that the 4.5 content might include aircraft which have been re-compiled since 4.4. That could change the rectangle IDs. Similarly, with Add-On aircraft, if they are updated, or make use of P3D default gauges, then they could have different rectangle IDs. I don't think L-M have any way of stopping this. Pete

Each version 9in fact each build) of P3D4 needs adifferent Active Sky build also. it is the DLL it installs that provides the radar information interface which FSUIPC (and other add-ons) uses. Pete

No. It sounds like you've not installed an up to date FSUIPC, which would have also installed the other documents. There would be ones for all three of the PMDG boeings. Pete

The latest version of MakeRunways uses the tool in;uded in its download. The use of the separate AddOnOrganise program is not longer automatic. Pete

The Prosim aircraft comes with a Lua plug-in to drive all the doors via those L:Vars. The works with keyboard assignments. But L:Var setting can be done with direct assignment in FSUIPC to macros instead. The Lua plug-in has the advantahe that the L:Vars control the amount the door is open, so the opening and closing is done in a loop over a number of seconds that way, not just open or close. And the door controls are "buttons" on my WideClient "buttonscreen", on a small touch screen in the cockpit, which is also used for many other things. None of this is relevant to other models. It just shows what can be done. Pete

Hmm. Very strange. I never had any option to automatially do this, and I used RC since it started (as an adventure language program) with FS98 all the way through to a few years back when I upgraded to ProATC/X and now to Pilot2ATC (as i like the voice interaction, better than menus). Yes, but based on your later posting it seems to be nothing to do with the BGL itself, but only to do with the non-copying of a file to RC. Before I even think about testing with a BGL I think you need to sort out what files you are using, when they were generated and which ones are actually applicable the the FB scenery and which not. Your finding now with R5 makes no sense. compare dates of generation to start with , and realte the files to the correct Runways.txt. Pete

Those keys (not your labelling) are the default sim assignments. FSUIPC is not involved. Where do your read which doors they are suppoesed to control? The sim only knows them as Exits 1, 2, 3, and 4. How those exit numbers are used varies from aircraft to aircraft. quite often the front and aft left exits are combined so that the forward and rear cargo ones can be separated. The labels you are getting from somewhere aren't really relevant. If those keypresses are whast is needed, those are the ones you use. You can ignore the labelling on your "homecockpit" (is that a supplier?) panel. the keystrokes are determined by your aircraft not by anything else. If there's no button for 4 doors separately you might need to make additiional assignments for the forurth or use the keystroke directly. I use a Prosim737 aircraft which has separate controls for all doors, even including the emergency overwing exits. Of course this can't be done with the 4 controls offered by the sim. it is done by L:Values in that case. i only mention it as an example of all the different implementations there can be. Pete

Hmm. that's odd. they are both produced at the same time in the same bit of code. The R5 one just contains an extra field or two (?). Well it isn't the scenery, just the definition of these things we are talking about. But there's no point is sending it in any case if you have R5 with the details included. Please send me the entries from the R5 file. Actually, probably better sending me both the R4 and R5 files complete please. Zipped they'll be quite small. Aha! So probably you haven't copied over the files RC needs since installing that airport. I didn't know RC automatically copied the files it needed. When I used RC I always had to do that manually. I'm not sure where you think FlightBeam have any responsibility to either MakeRunways or RC (the latter isn't even supported any more). That's odd. Pete