Pete Dowson

Well that would certainly explain it! FSUIPC cannot run until FSX loads it. it is a module within FSX, not a separae program! Best to use the [Programs] section of FSUIPC's settings to get the program automatically loaded at the start, (and optionally closed at the end). Pete

And no error message from FS_COM? If FSUIPC is running at the time (as you can see by its entry in the AddOns menu), then FS_COM has a problem. In that case it sounds like the first time was too soon, not allowing time for the Sim to be "ready to fly" -- which is when FSUIPC is ready to service applications. Sorry, but this is all adding up to be a definite problem with that FS_COM program. I'm afraid your only recourse is the supplier. Of course try reinstalling it first, or even re-downloading it as well. Pete

John has also pointed out to me that you have a lot of lines at the start of the INI file which will be ignored because they are not within a [section]. In fact it looks like you deleted something at the start and lost the [General] section. The one which will be used i later on in the file. Best do delete everything down to the line saying [JoyNames] Also, i missed other button assignments which aren't in the profile, some of which will nonetheless be applied because they buttons aren't overridden in the Profile:assignments. These are of particular note: 10=R0,7,C65607,0 - elev trim down, PRESS and REPEAT 13=R0,8,C65615,0 - elev trim up, PRESS and REPEAT 28=R1,1,C65607,0 - elev trim down, PRESS and REPEAT 29=P1,1,C65607,0 - elev trim down on 2nd device, same button, on PRESS I really don't know which actual buttons you are using for the actions you are reporting a problem with. But having so many assignments to the same actions is going to not only give confusing results but probably conflicting ones. There are also these two 30=R1,7,C65607,0 - elev trim down, PRESS and REPEAT 32=R1,8,C65615,0 - elev trim up, PRESS and REPEAT which will be overridden for the Profile by the assignments there, though the latter only has Repeat enable on one of the actions. i think you should delete the [Axes] and [Buttons] sections (both of each) and make new assignments. It would be easier than trying to sort this out. Here, I've done it for you. But first, please do UPDATE YOUR FSUIPC4! [JoyNames] AutoAssignLetters=No 0=BU0836A Interface 0.GUID={F412FB50-D532-11DF-8003-444553540000} 1=BU0836A Interface 1.GUID={F4132260-D532-11DF-8004-444553540000} [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [AutoSave] AutoSaveEnabled=No Next=10 Interval=60 Files=10 SaveOnGround=No 1=Thu 170008 2=Thu 170108 3=Thu 170207 4=Thu 170307 5=Thu 170406 6=Thu 175443 7=Thu 175543 8=Thu 180040 9=Thu 180751 10=Thu 165909 [GPSout] GPSoutEnabled=Yes Port=WideFS Speed=4800 Interval=2000 PosTo6Decimal=Yes Sentences=RMA,RMC,GGA,GLL,GSA,GSV,VTG,PGRMZ,AV400,GTEXT,RPY SimModeIndicator=No [GPSout2] GPSoutEnabled=No Port=COM0 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [ClientNames] 1=SERVER-MIP 2=PINO-FLYBOOK 3=SERVER-FSX 4=ENRICOQ 5=SERVER1-FSX 6=SERVER1MIP 7=MAGENTA [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=Yes ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=40 LeftBrake=-10578,-5862/8 RightBrake=-16116,16354/8 FlapStarts=-16384,410,819,2048,4096,6144,10239,12287,16383 FlapEnds=0,410,819,2048,4096,6144,10239,12287,16384 Flaps=0,16380/8 Aileron=-16380,-512,512,16380 Elevator=-11344,-1200,-1200,3154 Rudder=-16380,-512,512,16380/16 ElevatorTrim=0,0,0,0 SlopeElevator=-7 Rudder Trim=-16380,-512,512,16380 Spoilers=0,0 SteeringTiller=-16380,-512,512,16380 [Sounds] Path=F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Sound\ Device1=Driver audio principale Device2=Interfaccia SPDIF (SoundMAX Integrated Digital HD Audio) Device3=Uscita digitale (SoundMAX Integrated Digital HD Audio) Device4=Altoparlanti (2- C-Media USB Headphone Set ) Device5=Altoparlanti (SoundMAX Integrated Digital HD Audio) [Profile.prova 1] 1=Project Magenta 737-800 Paint1 (default) 2=Project Magenta 738 - Copia [JoystickCalibration.prova 1] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No FlapStarts=-16384,410,819,2048,4096,6144,10239,12287,16383 FlapEnds=0,410,819,2048,4096,6144,10239,12287,16384 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=-16380 MaxSteerSpeed=40 Aileron=-8936,94,94,13328 Elevator=-2206,3905,4370,10798 LeftBrake=-11235,-2250 RightBrake=-8424,2032 Flaps=0,16380 ElevatorTrim=-16380,-512,512,16380 Spoilers=-16380,16380 Rudder Trim=-16380,-512,512,16380 Aileron Trim=-16380,-512,512,16380 SlopeElevator=-4 Rudder=-9192,8235,8293,16384/24 SlopeRudder=15 SteeringTiller=-16380,1698,1698,16380 [General] UpdatedByVersion=4853 History=CSK6NHLTUT47JF1PKVO9Z InitDelayDevicesToo=No MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No DeleteVehiclesForAES=Yes AutoScanDevices=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=3 MinIce=-1 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=Yes SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=Yes EnableMouseLook=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=Yes OOMcheck=Yes WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0

First off, you are using a VERY old version of FSUIPC4. Please update that first. Second, you appear to have several assignments to most flight controls: Left Brake 0=0X,256,D,7,0,0,0 2=0Z,256,D,7,0,0,0 Both left and right brake 9=1Z,256,D,7,8,0,0 Right brake 1=0Y,256,D,8,0,0,0 4=0U,256,D,8,0,0,0 5=0S,256,D,8,0,0,0 11=1U,256,D,8,0,0,0 SteeriingTiller 3=0R,256,D,36,0,0,0 6=0T,256,D,36,0,0,0 10=1R,112,D,36,0,0,0 Not sure how many actual controls you have for all these things, but 4 right brakes and 3 tillers seems excessive? By contrast you only have 3 (THREE) buttons assigned: 0=P1,7,C65607,0 = Elev Trim Dn on button PRESS 1=R1,8,C65615,0 = Elev Trim Up on different button PRESS and REPEAT 2=P1,2,C65615,0 = Elev Trim Up on another different button PRESS Why two different buttons to trim Up? If one is captain and other first office, why not two of each? The lack of "repeat whilst pressed" is the reason for getting only one change per press, of course. The action only repeats if you ask it to by dselecting that option. Pete

Sorry, i've no idea what "FS_COM" is or what it wants with FSUIPC. Perhaps you need to look at its documentation or contact it's author's support? Who makes the MCP737PRO2? Pete

So they are both genuine serial port devices. Well done! You did it quicker than I could, I'm so unfamiliar these days with VRI devices! Pete

That's very odd. s I said, it works fine here. There are two other similar "logging" Lua plugins provided. Try them to see if they behave the same for you: VAS_Monitor display vals Pete

To the last point -- no, the menus can't be suppressed. Maybe the Message Window is off-screen or otherwise not visible? Check the FSUIPC INI file to see if the Window position is saved. If so delete the section for it and make sure that RestoreSimcWindows=No is set in the [General] section, not "Yes". Window positions are saved like this for example): [Window.Message Window] Undocked=599, 113, 1358, 76 [Window.SimConnect Message Window] Undocked=1197, 258, 364, 88 NewDocked=1433, 76, 650, 160 [Window.SimConnectWindow] Undocked=-693, 161, 596, 319 Also it might be saved in your saved Scenario file. Check that too. As for ALT TAB not working, there's really no way possible for FSUIPC or the Lua program to affect that. It is rather suspicious behaviour. Pete

If you don't need the flexibility of assigning the keys on the CDU to different things in FSUIPC (for example, for different aircraft CDU implementations), then it would be easier and more efficient to just make the Lua script send the relevant controls or keypresses. Functions for both of these are provided in the Lua ipc library 9see the Lua library document). Pete

Thinking about it further, I don't think FSUIPC can distinguish between two identical VRi units -- except by serial port number of course (which is at a lower level of code). I suppose that could have been a way of it assigning a different joystick number to each, but I'm sorry, development of FSUIPC4 ceased a while ago. It never came up when VRi serial port device support was "live", because If there was a real demand back then I'm sure it would have been implemented. I think it would still be possible by only declaring one of the devices in FSUIPC4.INI for default handling there, with the other being handled by a Lua plug-in. There is a document on handling VRi devices by Lua plug-ins in your FSUIPC Documents folder, and the "VRI_SetMach and VRI_SetBaro lua examples provided should also help. If all you wish to do is detect the button presses and assign them, you can either program them to set "virtual buttons" as in the HIDdemo lua or, probably easier and more efficient for a CDU keyboard, send the appropriate keypresses directly using the Lua library facilities. Pete

It works fine here with FSUIPC 5.151. In P3D4 the SimConnect message windows are suppressed if you don't have "Message Text" option enabled in the P3D4 user settings. The idea then is for you to use an external utility for the display (possible on a WideFS client PC). Check that option. Maybe you changed it? Pete

I'm afraid I don't know. Can you try VRInsight support? Pete

I'm afraid I don't have any PMDG aircraft installed, so I can't work this out for you, but possibly the macro needs editing to insert a different mouse action code? There's a list of these in the FSUIPC5 Advanced Users guide, on page 38. BTW the MCRO file contains 3 mouse macros, not just one. surely youu tested each one separately before combining them? The other possibility is that more time is needed between the three, or maybe only one pair of them. If they all work single, see which two can be paired, then make end 2=Display2 of the other(s) and program that on button release instead of press. Otherwise you might need to have three buttons assigned. Note that the best way to control PMDG Boeing aircraft is using their custom controls, all of which can be assigned directly in FSUIPC with no need for any mouse macros. Sorry. That's a question for PMDG or their users, on the PMDG website. Pete

Sorry, but access to these values isn't possible outside of the sim. Years ago when FSUIPC3 was still in deveopment or at least active support, then it would have been a relatively easy thing to do for you. Nut whilst FSUIPC3 is still supported in terms of help, there's no possibility now of any changes to the code. In fact the same now applies even to FSUIPC4. Only FSUIPC5 and associated utilities are still on the 'active' list. Pete

Sorry, I think you need to explain further. Do you mean that it isn't even logging the aircraft name? Or only that it is not selecting the Profiles you think you chose for them? So it IS recognizing the aircraft AND selecting the correct profile? That seems to contradict your first statement. So, please, precisely what DO you really mean? Well, certainly nothing in FSUIPC4 has chasnged for a long time. In fact 4.974 is still the same 4.974 it has always been. If you can describe exactly what you think is wrong, what has changed, then perhaps I can help solve it. Pete

Sorry, I've no idea, but most likely to do with disk layout. Two disks? Exactly the same formatted, exactly the same content, installed in the same order, the same way? I'm convinced there can be enormous difference between freshly installed setups and ones which have existed a while and "grown". in my own case, for example, I have changed my main P3D4 PC. The older one was a 7900X running 4.8GHz on all of 10 cores, the new one a 9900K at 5.5GHz on all 8 cores. A lot faster, right? Also the memory is faster -- 280MHz on the old one 3600 MHz on the new one. So some things would be faster, of course. The disks are both Samsung Evo Pro SSD M.2 devices, the installed and enabled scenery is the same. The P3D settings are the same (well,actually a bit more ambitious in the new one). The add-on are the same. The scenario's in P3D are the same. The old one loads up at UK2000 to a "ready to flly" state in nearly 10 minutes. Yes -- 10 MINUTES. The new one takes 82 seconds. There's no way that the high CPU and memory clock speeds can account for that sort of improvement.. It just has to be the cleaner layout on disk. Pete

I'm pretty sure it is IAS. TAS wouldn't make sense as performance is related o IAS and that's that you'd want to control.. (The Simconnect API isn't specific). It's probably the same as setting position, headin, speed etc in the Map. Pete

You should really read the Lua Plug-Ins document supplied. The [LuaFiles] section merely lists Lua files it finds in the Modules folder. It doesn't mean they get run. The only Lua plugins which get run automatically are: ipcInit.lua -- run during FS initialisation, and ipcReady.lua -- run when FS is ready to fly. For any others you have three options: 1. Add an "ipc.runlua" command to an ipcReady.lua file, or 2. Assign a key or button to the "Lua <name>" contorl in FSUIPC assignments, or 3. Add an [Auto] section to the INI file which contains one macro line: "1=Lua <name>" Pete

I've no idea. Is is a normal Game Controller as recognised by Windows? Is it recognised by P3D. Please get your FSUIPC installation up to date (current is FSUIPC 5.151), then after running it show me these files: FSUIPC5.INI FSUIPC5.LOG FSUIPC5.JoyScan.csv Find these in the Modules folder inside your P3D folder. You can ZIP them up and attach them. Pete

I saw your exchange with Umberto on the GSX forum, and added my own clarification. Basically this: First, the assignable FSUIPC control to list L:Vars just lists those extant at that time. The Lua plug-in I think you are using ("log lvars.lua") only polls for the ones it knows about. When it first runs it scans for L:Vars with IDs from 0 to 65535 building the array of names to keep watching. However, it stops doing that when it reaches the last valid ID in that scan. It does this for efficiency and with most add-ons this is quite sufficient.In this case, though, you would want it to repeat the complete scan, or at least continue from where it failed to retrieve a name before. it shouldn't be too hard to make such modifications. You'd just need to take care to avoid bringing the sim to a crawl or, on the other hand, missing changes to LVars because of the continuous re-scanning. We can discuss alternative changes if you are still interested, though if you need it for for own code then the simplest way would be to keep trying to read it by name till it appears and returns a valid numerical result. Pete

You are entering something wrongly. All THREE parts must be EXACTLY as specified -- Name, Email and Key. Please only ever post support questions to the main support forum. I have moved it for you. Also, NEVER put your key details in an open email. That may well cause it to be revoked and violates conditions of sale. State order number if you like, but not registration details. Order number is more useful. Pete

Ah, in that case you'll need to use the facilities to show the menu from RC elsewhere. But I assume you have to then take your VR headset off? That's really a need for Simconnect windows and menus to be scaleform. you need to register it as a future enhancement request. There are many SimConnect displays and menus from products which aren't under FSUIPC control. FSUIPC can intercept them and send them elsewhere (to a Lua plug-in or another PC via WideFS, for example). But I don't think it should re-route P3D displays it intercepts back to P3D in some other form. that should be done directly in P3D. You'd need to get someone to write a module which a Lua plug-in (or maybe other program) could call which deals with this Scaleform system, whatever it is, and sends it back into P3D -- if that is possible. Sorry, i only know the SimConnect interface. Pete

No, it asks direectly. What I was describing was how this Listing (the FSUIPC control and the Lua plug-in provided) works. You call for a pecific LVar would simply return nil is it didn't exist. A zero? If i remember rightly (which I may not, getting too old) you should get "nil" which is the Lua "non-existent". Which script is that? Pete

Blurries are normally a sign that your fiber time fraction parameters is set too low. You should increase it, or try using the Dynamic FFTF utility which I have found very useful. It can reduce the fraction to increase FPS when necessary and increase it when performance is good. You can set it by FPS thresholds or by altitude. I don't think there's been any change in "blurriness" problems in any versions of P3D so far. The main wish for many is better sharness for photo-real screneries, and i think that's being attended to in any case. Many are expecting 4.5 to be released withing weeks if not days. hy not wait and try that? Don't forget, when updating P3D or your video drivers, to delete your shaders so they can be properly rebuilt. Pete

No, it simply isn't in the list. FSUIPC asks P3D for the count of L:Vars (say 'N'). It then iterates through those numbers, or "IDs", from 0 to N-1 to get the names. It cannot know about any which don't exist at that time, and cannot really cache any names you throw at it to record their "non-existence". You'll see in the Lua library document that these functions are represented clearly by ipc.getLvarId (getting the numerical ID given a name). and ipc.getLvarName (the reverse, getting the name given the ID). Both will tell you if it exists or not. I've got GSX working again now, so I could check here for you in the next few days, but it appears that isn't needed now? Pete