Pete Dowson

Are these commands in such frequent use, then? Not activated by button press of keypress? I can't imagine one of those commands in the macro taking very long on a single invocation. And what do you mean "starts to lose fps"? Is this progressive, then? I think you really do need to supply a lot more information -- like what these macros are, how they are invoked, and provide a full description of what happens. AND, as always, provide version numbers of the software you are using. Pete

Probably, but try using Google, as we would have to. This is a support forum for FSUIPC and related flight simulator add-on software, not Windows. Pete

As it says, 5620 is 7% and 16383 is 100% (well, on the ground -- bear in mind that in flight the maximum the spoiler really goes to is about 70 or 80% (don't remember which). In the latter case it is known as "speedbrake" rather than "spoiler"). So, if you want x% then if x < 7, don't bother. Otherwise, consider 93% is spread over (16383 - 5620) points in this scale. So 1% = 10763 / 93 = 115.73, near enough. So for x% where x >7, you'd use 5620 + ((x - 7) * 115.73), rounded down to an integer. It's really neither FSUIPC nor SimConnect, just the way that axis works internally. Note that this is not the same in MSFS. Pete

There's no "demo" version. The unregistered install is fulfilling FSUIPC's real purpose, the reason it was written in the first place: to act as an FS interface to applications, one which has remained compatible over the years across all of the FS versions and derivatives since FS98 days. So, unless you have such programs (ones which make use of FSUIPC in this way), FSUIPC is no use to you until you purchase it. Please peruse the installed documents -- especially the main User guide -- to see what it does for you if you purchase it. Then decide. (You'll find the documents for FSUIPC7 installed in your Documents folder, in the subfolder called "FSUIPC7"). Pete

The "UseProfiles" parameter defaults to "Yes". See this section entitled Automatic conversion of existing profiles in FSUIPC4.INI in the "Profiles in separate files" document. Pete

Correct. It's just a 32-bit value ("DWORD"). If you want to use a value with fractional parts, depending on the range you need, I would use a decimal multiplier on the value you need before entering it in the assignment, and divide it by the same in the plug-in. I'm afraid strings aren't possible in this context. Pete

Okay. I've tested this both in FSUIPC6 and FSUIPC7 and the action of that PM control is exactly as prescribed -- it toggles bit 24 in offset 5414. that accords with the PM documentation for the ALT button push. You are lucky I noticed your PM to me (I don't see these most of the time). Why a PM just to attach logs? You can do the same here. Anyway, both the FSUIPC and WideClient logs show the bit correctly toggling on and off when you use the assigned button. The FSUIPC log shows it clearest: 373375 Monitor IPC:5414 (U32) = 0x1000000 379641 Button changed: bRef=0, Joy=158, Btn=13, Pressed 379641 [Buttons] 2=P158,13,C2056,0 379641 FSUIPC Control Action: Ctrl=2056, Param=0 379641 PM action: 5414 bits toggled: 0x01000000 379641 Monitor IPC:5414 (U32) = 0x0 379641 JoystickValues PCnum=0, dwCount=1, data[2]={0000009e 00406010} 379844 JoystickValues PCnum=0, dwCount=1, data[2]={0000009e 00404010} 379844 Button changed: bRef=0, Joy=158, Btn=13, Released 380344 Button changed: bRef=0, Joy=158, Btn=13, Pressed 380344 [Buttons] 2=P158,13,C2056,0 380344 FSUIPC Control Action: Ctrl=2056, Param=0 380344 PM action: 5414 bits toggled: 0x01000000 380344 JoystickValues PCnum=0, dwCount=1, data[2]={0000009e 00406010} 380359 Monitor IPC:5414 (U32) = 0x1000000 The WideFs log shows this too, though of course the joystick button action isn't logged there. So your problem is definitely a matter for PM support, which I hope is still active. Note that, whilst I've not used PM for about 5 years, I did use it and was quite closely involved with Enrico on that project since FS98 days -- that's why there are so many PM-specific things built into FSUIPC. With other avionics system add-ons like Sim-Avionics and ProSim the offset management and assignment methods were left to the project developers. I'm now a confirmed ProSim user. ProSim have largely moved over to using SimConnect directly rather than through FSUIPC. Pete

Hmm. For me cloud shadows are the worst. Too dark. I makes my otherwise gorgeous TrueEarth or Orbx Europe scenery looks so dark on overcast days, really a waste of my nice wide screen and 4k projections! Building shadows do make airports looks more realistic. Pete

So, maybe you need to go over to PM support then. But do post back when you have the answer. Actually, this doesn't look correct: 373375 Monitor IPC:5414 (U32) = 0x1000000 So bit 24 was set then. The next part is 3 seconds later: 379641 Button changed: bRef=0, Joy=158, Btn=13, Pressed 379641 [Buttons] 2=P158,13,C2056,0 379641 FSUIPC Control Action: Ctrl=2056, Param=0 379641 PM action: 5414 bits toggled: 0x01000000 and despite the correct control being instigated, bit 24 hasn't changed. Was that the first time you pressed the button in this session? All offsets start off as zero, so unless PM set that bit before that log section, the use of the button must have. Using the button again probably should have toggled the bit off. I'm not sure offhand -- maybe PM should be turning it off when it has seen it. i'll need to check the code in FSUIPC. But not now, it's late and i'm off to bed. I'll check in the morning. Pete Pete

What about the anti-aliasing options -- always a bigger performance difference for me, even one notch on each setting can make a big difference. Then there's shadows which have a stupid impact for me (so i always have them all off, though sometimes I could have some on at least)). And the LOD value (distance with detailed textures). Of the performance settings it's really perhaps only the traffic slider that was made adjustable on the fly. Pete

The added control PM AB ALT button push should be okay. It only toggles a bit in a PM offset (bit 24 in 32-bit offset 5414) which PM then responds to. Can you do some logging, please. In the Log options enable 'Buttons and Keys' and in the Offsets option enter 5414 as type U32, with Hex checked and Nromal Log selected below. Just do this when you are ready to test your assignment, then try that and then get the FSUIPC7.log and show us what it says. Pete

Yes, but these days I'm using a utility by Thomas which is excellent, (but as yet unreleased). RTSS appears to give misleading measurements when using more than one 3D window. Pete

Hi Ray, I don't think there are any controls to change UI Menu settings. It would be nice to be able to change quite a lot of things 'on the fly' so that frame rates can be maintained automatically by changing items -- especially those controlled by sliders. But in the case of Dynamic Lighting, why not just run with it disabled in any case. I know you don't fly at night, so what difference would you see? I need it enabled because my Prosim model 738 needs it enabled. Luckily (I suppose) I've never noticed it affecting my frame rates particularly. But then i'm using P3Dv5 which gives me so much better performance than P3Dv4 that the hit (if there still is one) goes unnoticed. Pete

If you take another look at Buttons and Switches, you'll see that you can assign two actions to the switch -- on to operate when "pressed" and the other when "released". Now I know that such terminology is really applicable more to buttons, but the "on" state of your switches is effectively a "press" (because that's exactly what it looks like to the system), and conversely the "off" state is seen as a "release". So of course you can program your 'off' action too. What, like a timeout? I wonder why anyone would want such a feature? Hmm. Some users have the exact opposite opinion it seems. For me they are both valid approaches and each just as usable (and I write now as more of a user -- here I just help out with support. I still look after my freeware though, like MakeRunways). Running within the Sim does bring performance advantages -- SimConnect exchanges are direct not via TCP/IP or Pipes, Controls and Keys being sent are almost immediate, and there's access to internals if needed. (Done by hacking into code before P3D4 days, but via new interfaces since then -- PDKs, program development kits available for internal addon -- aircraft as well as utilities like FSUIPC and GSX). Pete

The answers are all in the FSUIPC sales page on Simmarket. Whilst the registration is done via the installer, as before, the process is fast and painless, also as before. Pete

C:\ is probably not a good choice -- maybe to write there you need the program to have Administrator rights. Your documents folder would be a better choice. Apart from the radar.bin file, which I direct to a dedicated flight sim drive also containing ProSim, I also use the Bitmap path parameter to send an always-viewable BMP version to the P3D documents folder. Pete Pete

Thanks. These added sections at the end don't make sense: [Area.2000] Title=RJAA Tokyo Narita P3D Local=G:\P3DV5\Addon Scenery\RJAA Tokyo Narita P3D Layer=2000 Active=TRUE Required=FALSE [New York CIty X] Active=FALSE Those last two lines are definitely an error and should be deleted. I'm not sure whether 2000 is a valid section or layer numbe either. Maybe replace 2000 by 193, the next layer number available. Otherwise I don't see anything wrong with it. If the corrections above don't help, it must related to an AddOn.xml file. If so I think Oliver (author of the Lorby program) will need to look at this. It's to do with that program. Try using his AddOnOrganiser, please? It is better at defining what is going on and may indicate this error directly. If you don't already have it I recommend you install it immediately. it is very useful. Get it from https://www.lorby-si.com/downloads.html#. It's listed as "FREE: Lorby Prepar3D Addon Organizer" Pete

Okay. The reason for your problem is shown in those files MakeRunways is working correctly: LorbySceneryExport executed: Checking for "MakeRwys_Scenery.cfg" Reading Prepar3D v5 scenery: The CFG file being used is: "G:\P3DV5\MakeRwys_Scenery.cfg" but the file generated by the Lorby program is wrong. All it contains is: [General] Title=Prepar3D Scenery Description=Prepar3D Scenery Areas Data Clean_on_Exit=TRUE [Area.001] Title= There's no scenery listed at all! That's why MakeRunways doesn't produce any data files. So, there seems to be something wrong with your scenery.cfg file, the one in your P3D folder in ProgramData. See what that looks like. Pete

I managed to check MakeRwys on a Win7 PC, and I get the same crash. I'm afraid the latest version of MakeRunways is definitely not compatible with Windows 7. I'll see what I can do about that, but if it means downgrading any of its newer actions I'm afraid that's it, i'll document it as for Win10. Meanwhile you can try using an older one. I've re-uploaded version 4.70 for use with Win7 and it is perfectly adequate for FS2004: MakeRunways_470.zip Pete

Okay. Silly mistake in my previous fix. Please try BETA2, now downloadable MakeRwys510BETA2.zip Pete

Hmm. Very odd. Is a Runways.txt file produced? If so please show me its contents so I can see where it got to. Pete

I've moved your question from the FAQ reference subforum (NOT for support questions) Division number? Why are you calling it that? They are flags for the options you can set in the calibration pages like No Reverse Zone and 'Rev'. What is concerning you? You don't need to know the encoding for calibration -- just look at the calibration pages in the FSUIPC options. The -512,512 values define the default 'centre' zone assuming this is used. Again, what is worrying you? Please always post questions or support requests to the correct place . Pete

But the list of Taxi Points (in Runways.Txt) now definitely includes all of them, beyond #4095 which is where it stopped before. It looks lie even though it now gets the complete list it still only uses the first 4095 in its linking! Working on it now ... Pete

Please show me the FSUIPC log and ini files. One thought: did you install ASP4 after FSUIPC? if so please try installing FSUIPC again. I think the order is quite important (for reasons neither I nor HiFi ever fathomed). Pete

Yes, could be. The current version is developed using Visual Studio 2019, with the latest libraries, so that it can take advantage of the latest developments. What version of Windows are you using? Didn't you see that question in my previous response? You might do well installing the following, assuming they will install on whatever version you are using: vc_redist.x86.exe vc_redist.x64.exe Let me know. Otherwise I'll see if I can dig up a many-years old version, suitable for something as old as FS2004. Pete