Pete Dowson

Yes, but so does Flight Sim! You'll find that, if you ever try adding scenery layers to the library using the FS dialogue instead of allowing an installer to do it. The path should ALWAYs be to the folder above, the one containing both Scenery and Texture sub-folders. In fact I am VERY surprised that FS/P3D doesn't object to the path -- and I would have fully expect it not to load the scenery. Seems it might be more flexible that anyone gives it credit for. Best report the installer's wrong entry in the CFG file to Aerosoft. It must only apply to the P3D version, because it didn't happen here! Pete

No, don't reinstall anything. Just run one or more of the SimConnect.msi's. L-M don't seem to be bothered at all about FSX SimConnect add-ons and P3D doesn't install ANY FSX SimConnect versions by default, it only supplies them for you to install. You should probably install both the SP1 and the SP2/Acc versions for best support of FSX add-ons. I've no idea why my work-around, supplying and installing my own DLL, doesn't work on some folks' systems. The file is there but Windows simply doesn't see it or doesn't allow access to it! Pete

The currently supported version of MakeRunways is 4.696. Nevertheless, the Airport Facilities BGL in your LEPA add-on evidently doesn't have a BGL wuch has these details in a form recognised by FSUIPC. I have the Aerosoft Palma airport too, but only for FSX (though I use it in P3D too). The entries in the Scenery CFG here are [Area.210] Title=LEPA_EVO_TERRAIN Local=E:\FSX\aerosoft\LEPA_EVO_TERRAIN Layer=210 Active=TRUE Required=FALSE [Area.211] Title=LEPA_EVO_AIRPORT Local=E:\FSX\aerosoft\LEPA_EVO_AIRPORT Layer=211 Active=TRUE Required=FALSE and the resulting entries in the Runways.TXT file, the main log, are 4-fold: Area.210 "LEPA_EVO_TERRAIN" (Layer=210) Path(Local/Remote)=E:\FSX\aerosoft\LEPA_EVO_TERRAIN ============================================================================= Area.211 "LEPA_EVO_AIRPORT" (Layer=211) Path(Local/Remote)=E:\FSX\aerosoft\LEPA_EVO_AIRPORT ============================================================================= E:\FSX\aerosoft\LEPA_EVO_AIRPORT\scenery\AFX_LEPA_20.BGL ============================================================================= Deletions check for Airport LEPA: Delete all taxiways! Delete all runways and starts! *** DelBth *** LEPA0061 Lat 39.547138 Long 2.710691 Alt 24 Hdg 59 Len 10720 Wid 148 ILS 110.90, Flags: GS DME BC *** DelBth *** LEPA0062 Lat 39.541378 Long 2.731988 Alt 24 Hdg 59 Len 9836 Wid 148 *** DelBth *** LEPA0241 Lat 39.555462 Long 2.761831 Alt 24 Hdg 239 Len 9836 Wid 148 ILS 109.30, Flags: GS DME BC *** DelBth *** LEPA0242 Lat 39.562496 Long 2.743215 Alt 24 Hdg 239 Len 10720 Wid 148 ILS 109.90, Flags: GS DME BC Delete all helipads! Delete all taxiways! COM: Delete all frequencies! ============================================================================= E:\FSX\aerosoft\LEPA_EVO_AIRPORT\scenery\AFX_LESB_04.bgl ============================================================================= Deletions check for Airport LESB: Delete all taxiways! Delete all runways and starts! *** DelBth *** LESB0060 Lat 39.596565 Long 2.697772 Alt 135 Hdg 60 Len 3281 Wid 72 *** DelBth *** LESB0240 Lat 39.601204 Long 2.707784 Alt 135 Hdg 240 Len 3281 Wid 72 Delete all helipads! Delete all taxiways! COM: Delete all frequencies! ============================================================================= E:\FSX\aerosoft\LEPA_EVO_AIRPORT\scenery\AFX_LEPA_20.BGL ============================================================================= Airport LEPA :N39:33:06.7875 E002:44:18.1318 24ft Country Name="Spain" State Name="" City Name="Palma De Mallorca" Airport Name="Palma De Mallorca" in file: E:\FSX\aerosoft\LEPA_EVO_AIRPORT\scenery\AFX_LEPA_20.BGL Runway 6L/24R centre: N39:33:17.3480 E002:43:37.0602 24ft et cetera (it's a very large entry so I've not included it all). The main difference is the inclusion of "\scenery" in the paths you have in your SCENERY.CFG file. I'm sure that should NOT be there. Paths in the Scenery.CFG file should always be to the folder which contains the Scenery and Texture folders.. Pete

Well, check with a default aircraft first. If those axes work then, it is to do with which axis controls your add-on recognises. Perhaps you are assigning in FSUIPC as "direct to calibration" when it is instead expecting and intercepting only the current "Axis mixture ..." controls. Try also with calibration in FSUIPC for those axes disabled. Pete

The answer is to actually install SimConnect yourself, as pointed out in the pinned topic "P3D Version 3: FSUIPC menu entry not appearing" at the top of this forum. Pete

The only ones currently available and labelled for FS2004 (or FS9) and before on the Schiratti site, as pointed to by the SimMarket purchase page, or in the Download Links subforum above. There's only ever one version of FSUIPC3 available, and one version of WideFS6. Pete

Is this with default aircraft, or only specifically with some add-ons? You can enable axis logging in FSUIPC's Logging Tab and check that the Mixture controls are being sent. If you temporarily run in Windowed mode and enable the console log you can see the results in real time. Also check that there's nothing conflicting assigned n P3D itself. Best to disable controllers altogether in P3D. Pete

Sorry, I have absolutely no knowledge of SPAD, and I avoid Saitek gear as much as possible. Is there no support or documentation for SPAD? Pete

Hmm. doesn't do it for me. Interesting, though, that you have absolutely no calibrations in FSUIPC whatsoever. So how come the worry over "slopes" buttons"? Are you in the Calibrations tab just out of curiosity? There aren't even any assignments to any axes at all, even though you have some buttons assigned. You aren't leaving controllers enabled in FS whilst assigning in FSUIPC, are you? That's asking for trouble in any case. You even have three profiles with absolutely no assignments or calibrations in any of them! There is one curio in the INI. This line (in the Calibrations section) makes no sense whatsoever: MaxSteerSpeed=Q10,128,9168,65535 That looks like some sort of corrupted calibration assigned to the wrong keyword. The MaxSteerSpeed is just the ground speed at which the rudder takes over 100% of steering from the Tiller, assuming both are assigned. It's just a simple number! Pete

It can't be anything to do with FSUIPC4 -- the assignments are there and the same for both profiles. It must be some interaction between the Cameras.CFG file and the actual aircraft CFGs. In fact I has always assumed that the numbered cameras (0-9) were only defined in the CAMERAS.CFG, but then this is an area I know nothing about I'm afraid. Pete

It sounds identical to the previous problem. The Arcaze board is probably re-registering itself. Haven't you used that utility mentioned by Reinhard to check what is happening? FSUIPC can only react to what Windows tells it. Arcaze boards seem very problematic to me. Pete

I know nothing about OpenCockpits hardware or SIOC, but the latter has plenty of users and you should be able to find help with the scripts. Try the cockpit builders forums over on MyCockpit (http://www.mycockpit.org/forums) Pete

Confirming that all is well if you refrain from renaming the EXE, except thaat those errors are still present: 234 Hook Error: can't find .1543569056 in SIM1.dll 234 Hook Error: can't find .1543569056 in VISUALFX.dll I'm wondering if that's either due to an out of date version of ASN, or the wrong order of loading DLLs. The ASN entry in that file should be last, something which, when run, ASN normally detects and puts right (telling you to restart FS). Maybe it only does that if you run it after FS. Pete

There's the problem. You aren't running Prepar3D but "Kodiak". Why? Renaming the main object program creates havoc not only for FSUIPC but many other programs which relay on seeing the correct process name! Rename it back to Prepar3D.exe, or (less favourably) rename your .KEY file accordingly, same as your INI and LOG files. This latter method, for renamed EXEs, is described in "Multiple INI Files", page 48 of the FSUIPC Advanced User's document. Anyway, you can bypass the start up screen by adding SHOW_OPENING_SCREEN=0 to the [sTARTUP] section of your Prepar3D.cfg file (as in FSX.). You also appear to have another (bigger) problem with a corrupted P3D install, causing these errors: 172 Hook Error: can't find .1526660768 in SIM1.dll 172 Hook Error: can't find .1526660768 in VISUALFX.dll though it is vaguely possible this could be derived from the same mis-naming action. Pete Pete

I don't actually know there is a Forum, but there is a website -- I found it like anyone else could by Googling! It's fs-linda.com. The picture there of the LINDA front end program does appear to have a Support Forum selection you can make, bottom right. Have you not tried that? Pete Pete

FSUIPC is not a hardware driver. It accepts joystick and button inputs which follow Windows standard joystick interface, but there is no standard interface for output -- displays, indicators and so on. That all depends on what the device actually does, how it is connected, what Windows drivers are installed for it. To make any indicator display work you need 1. A physical connection supported by a driver which Windows recognises. 2. A program to read the FS values to be displayed, and send them to the device using whatever protocol or methods have been implemented in the driver for that device. Doesn't the OpenCockpits board come with software, a driver, or any instructions? If it simply interfaces the device to Windows as a HID device ("Human Interface Device", then it could probably be driven from FSUIPC by a Lua plug-in program using the HID facilities in the COM library. But this would certainly need investigation into precisely which bits and bytes do what, and then writing a program. Pete

You seem to have posted something like this in a different thread. If the question is about LINDA then maybe it would be better in their Forum? Pete

Ports are listed by Windows Device Manager, under "Ports (COM & LPT). If you are using the VRi software for your device then it is up to that. If you are using the FSUIPC provisions then are you running one of the programs to link the real port to a virtual one? Pete

That's very odd, as it shouldn't! I can't make it do that here. Can you show me your INI file please-- paste it here. Maybe somehow some Slopes parameters have got into your INI for those, which might do it. Pete

Okay, I've looked at this. In fact it was listed as a change in FSUIPC versions 4.25 (February 2008) and 3.80 (March 2008). Here's the entry in the History document (in your FSUIPC Documents subfolder): A bug is fixed which affected the calibration of the four separate Mixture axes. The bug caused the output values to jump from 8192 to around 12288. This was due to the attempted provision of asymmetric slopes for off-centred “centres”. The Slope option is no longer offered for these axes. If you really need slope facilities on those axes I could make an INI file option for you to release the restriction, but then it would be your choice, your risk. Let me know. Also if you could explain why, it would help. After all no one else has worried about this for 8 years! Pete

The currently supported versions are 4.949f or 4.049g. Hmm. Interesting. What a good find! Actually, here, none of the Mixture axes on Page 4 of 11 have Slope buttons. I wonder how long it's been like that? Maybe forever, and no one noticed? (I doubt very much many folks put slopes on anything but aileron, elevator, rudder, throttles and maybe brakes). I'll look at that and have it fixed on the next release, probably next week. Thanks, Pete

Well, according to that log, FSUIPC is operating as fully registered. I don't know why you think it isn't? But I do see that the system date and time was over 4 weeks ago when that Log was produced: 63 System time = 26/01/2016 19:25:05 Was that the last time you tried loading P3D3.1, or is the date incorrect on your PC? I also see that FSUIPC didn't actually start up fully. Not sure why that is, but you should note that 4.949 is not the currently supported version. Best to download and install the current one, 4.949f, please (or even the interim update 4.949g), and try again. Pete

FSUIPC uses standard Windows functions for this, and actually has no direct control over when or whether drop downs are open or not. I suspect another add-on is doing something in the background which might temporarily change focus. I think if focus is diverted from a drop down it does close. In fact, apart from making an actual selection I think that's the only thing that does do this. You could also try temporarily running FS in Windowed mode to see if that makes any difference. If it does it may be related to some video or video driver setting. Pete

You reported this twice. Please see other thread reply. Also, looking at the log, the hang is occurring at the exact point where FSUIPC is scanning your joystick devices -- is it possible that you have some old joystick driver relating to a now disconnected device? I've seen some drivers hang whilst scanning a missing device. To check this you can temporarily de-register FSUIPC by renaming or removing the FSUIPC4.KEY file from the Modules folder. An unregistered install won't be scanning devices. Pete

Find the FSUIPC4.LOG file, n the P3D Modules folder, and show that to me, please. Pete