thestuntman

I have moved SIMstarter out of Program Files and onto my D drive but now I get an error saying "Access to the path "C:\ProgramData\Lockheed Martin\Prepar3d v3\Simobjects.cfg is denied". I've never had this before so somewhere along the line my permissions have been messed up. I haven't changed anything to do with permissions so it must have happened when running SIMstarter as admin. When P3D loads it is not using the modified scenery.cfg file again either. It uses the one in the VirtualStore folder unless i run as admin.

I'll do that as soon as I get home. I did find out that SIMstarted was using C:\Users\Josh\AppData\Local\VirtualStore\Program Files (x86)\SIMstarter as it's root folder instead of c:\Program Files (x86)\SIMstarter. Running it as Administrator worked after i copied the profiles over to the correct folder.

The log file is empty, even though debugging is turned on in the options. I am using version 2.7.4. Every one of the User Profile .cfg files in the SIMStarter\Uer Profiles folder. (PREPAR3Dprofile02_config.cfg for example) is pointing to the same scenery set .cfg file (scenerySet=PREPAR3Dscenery1.cfg;), and that file has the Mastery Scenery set which is everything that I have installed which is not what I want. I'm not sure why this is as every profile is setup differently. I tried deleting all the User Profiles .cfg files and all my profiles are still there. Is there another folder where they are stored? Edit: Running as administrator recreated all the .cfg files I deleted as a test in the SIMStarter\User Profiles folder, but I have no scenery sets or anything saved. If I run as a normal user, my sets are still there but the program does not modify scenery.cfg again.

I have had an issue where SIMstarter will not modify the scenery.cfg file no matter what profile or scenery sets I choose. scenery_lastSIMstarterProfileRun.cfg is being written correctly, but it is not being copied over to scenery.cfg. I have a feeling it may have to do with the OrbX region switching

I haven't had any of those problems. My yoke is always recognised correctly. I am only able to get things working if I use offsets in FSUIPC rather than sending normal FS Controls but this doesn't work with some payware planes. As an example, elevator trim does not work, the correct control IDs are sent to FS according to the logs (either if I use Linda or remove it and just use FSUIPC), but nothing in sim happens. Changing the button mappings to use offsets and trim works, but it will not work in PMDG 737 for example.

Seems like it's a problem with FSUIPC. Linda is sending the correct control ID to P3D it's just not doing anything with it. As a test i got rid of Linda and used FSUIPC to map the same button to the same control Button 2 should roll the Trim wheel nose down but it doesn't 265063 [Buttons] 2=R0,2,C65607,0265063 Repeating flag set: bRef=0, Joy=0, Btn=2 (RepeatDelayCtr=11)265063 FS Control Sent: Ctrl=65607, Param=0265094 Button changed: bRef=0, Joy=0, Btn=2, Released Yet if I manually roll the wheel by clicking on it it fires the exact same Control ID 265500 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN So if P3D is completely ignoring any controls sent to it by FSUIPC then it's no wonder Linda doesn't work. It's doing it's part fine. It works with offets as well, but the Linda module for most planes does not use offets, at least the ones I have tested the most eg PMDG Elevator trim sends Ctrl=65607 and 65615, but with P3D ignoring control IDs it doesn't work. It also works with keystrokes, but native FS Controls are a no go.

Same problem. What is wierd is that SOME controls work. For instance if I map the PMDG 737's Autopilot CRS Left dial to buttons on my throttle quadrant, that works, but Flaps won't, trim won't. Pretty much all the standard FSX controls don't, and for some reason, a lot of the standard FSX controls aren't working with FSUIPC any more either. The controls are sent according to the log, they just don't do anything in the game, but if I map them using the standard P3D Settings menu, everything works.

Sent. I am still getting FS Control Sent: Ctrl=65607, Param=0 FS Control Sent: Ctrl=65615, Param=0 in the console window, so something is sending controls to P3D but nothing is actually happening. Nothing assigned in FSUIPC but axis. Same thing happened before and after.

That was copied from the Linda console. The only drivers I have for my Yoke are the standard Windows 10 drivers with SaiD0BAC.pr0 renamed so I can use the Mode switch button. I have the full paid FSUIPC. I was using it previously with my old Logitech stick with no issues. I have also notice Linda is creating a file named something like config-hid-1602200951.lua in linda-cfg\system almost every time it is run. There are now 27 of them, all the the same contents.

As an update I started setting up the RealAir B60T which has a module. The controls for hiding and showing the yoke in the VC work, but I can't get any of the standard FSX controls to work, ie trims, flaps, landing gear etc.

I am using Linda 2.6.7 with P3D 3.1 and a Saitek Yoke and I am not getting any controls working in P3D. I have a brand new FSUIPC.ini after backing up my old one. Axis assignment is still done through FSUIPC like always, and all Joystick buttons have been removed from P3D's settings Linda seems to be sending controls to P3D but they aren't actually doing anything in the sim. Elevator, Ailerons etc assigned through FSUIPC work but nothing else. I have made a module for the Maule M7 that comes default with P3D but it is just a clone of the standard Default Module. Linda picks up my yoke perfectly and I can assign buttons, and as you can see in the log below the controls are being sent. ---------------------- Joystick Device Scan ----------------------- Product= Saitek Pro Flight Yoke Manufacturer= Saitek Vendor=06A3, Product=0BAC (Version 3.4) Serial Number= Saitek ------------------------------------------------------------------- LogOptions=C0000000 00000001 ------------------------------------------------------------------- ------ Setting the hooks and direct calls into the simulator ------ --- CONTROLS timer memory location obtained ok --- SIM1 Frictions access gained --- FS Controls Table located ok --- Installed Mouse Macro hooks ok. --- Wind smoothing fix is installed --- All links okay (except older global weather setting method) ------------------------------------------------------------------- SimConnect_Open succeeded: waiting to check version okay Trying to use SimConnect Prepar3D Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0) Initialising SimConnect data requests now FSUIPC Menu entry added Weather Mode now = Theme D:\games\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air C:\Users\Josh\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml D:\games\Prepar3D v3\SimObjects\Airplanes\Maule_M7_260C\Maule_M7_260C.air E:\Josh\Documents\Prepar3D v3 Files\Test.fxml KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4 .. Key not programmed -- passed on to FS System time = 20/02/2016 00:56:23, Simulator time = 11:58:15 (01:58Z) Aircraft="Maule M7 260C" Starting everything now ... ASN active function link set Ready for ASN WX radar Advanced Weather Interface Enabled FS Control Sent: Ctrl=65603, Param=0 FS Control Sent: Ctrl=65595, Param=0 FS Control Sent: Ctrl=65595, Param=0 FS Control Sent: Ctrl=65595, Param=0 FS Control Sent: Ctrl=65603, Param=0 FS Control Sent: Ctrl=65595, Param=0 FS Control Sent: Ctrl=65603, Param=0 FS Control Sent: Ctrl=65595, Param=0 Sim stopped: average frame rate for last 75 secs = 29.7 fps *** Entered Buttons option page *** FirstButtonChange res=00000008 (0.0, 8) *** Exiting Buttons option page *** *** Entered Keys option page *** *** Exiting Keys option page *** FS Control Sent: Ctrl=65603, Param=0 FS Control Sent: Ctrl=65595, Param=0 FS Control Sent: Ctrl=65570, Param=0 FS Control Sent: Ctrl=65570, Param=0 FS Control Sent: Ctrl=65607, Param=0 FS Control Sent: Ctrl=65607, Param=0 FS Control Sent: Ctrl=65607, Param=0 FS Control Sent: Ctrl=65607, Param=0 FS Control Sent: Ctrl=65607, Param=0 FS Control Sent: Ctrl=65615, Param=0 FS Control Sent: Ctrl=65615, Param=0 FS Control Sent: Ctrl=65615, Param=0 FS Control Sent: Ctrl=65615, Param=0 FS Control Sent: Ctrl=65615, Param=0 FS Control Sent: Ctrl=65615, Param=0 FS Control Sent: Ctrl=65827, Param=0