Greekbull Posted September 5, 2016 Report Posted September 5, 2016 (edited) Hello, I seem to be having an issue with FSUIPC4. It loads up in game. Is visible in my addons file. I've watched a couple of tutorials and have loaded in some button and axis commands which seem to take and save in my user created "Superbug" profile. But when I go back in game none of the commands are working. I did uncheck the enable controls or commands in FSX. I tried getting rid of the dll file and even deleting and reinstalling with the same result. It was also not the first time I'm running FSX so that shouldn't be an issue. Here's my log: ********* FSUIPC4, Version 4.955c (14th June 2016) by Pete Dowson ********* Windows version reported as 6.2.?.9200 fsx.exe version = 10.0.62615.0 Reading options from "E:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 8.0 or later Module base=58740000 FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 234 System time = 05/09/2016 18:11:02 234 FLT path = "C:\Users\ptsar\Documents\Flight Simulator X Files\" 234 ------ Module Version Check ------ 234 acontain.dll: 10.0.62615.0 234 api.dll: 10.0.62615.0 250 controls.dll: 10.0.62615.0 250 fs-traffic.dll: 10.0.62615.0 250 G3D.dll: 10.0.62615.0 250 language.dll: 10.0.62615.0 250 sim1.dll: 10.0.62615.0 250 visualfx.dll: 10.0.62615.0 250 weather.dll: 10.0.62615.0 250 window.dll: 10.0.62615.0 250 ---------------------------------- 265 Trying to connect to SimConnect Steam ... 281 FS path = "E:\Program Files (x86)\Steam\steamapps\common\FSX\" 390 ---------------------- Joystick Device Scan ----------------------- 390 Product= Throttle - HOTAS Warthog 390 Manufacturer= Thrustmaster 390 Vendor=044F, Product=0404 (Version 1.0) 390 Serial Number= Thrustmaster 390 Product= Joystick - HOTAS Warthog 390 Manufacturer= Thustmaster 390 Vendor=044F, Product=0402 (Version 1.0) 390 Serial Number= Thustmaster 390 Product= Saitek Pro Flight Combat Rudder Pedals 390 Manufacturer= Saitek 390 Vendor=06A3, Product=0764 (Version 2.1) 390 Serial Number= Saitek 390 ------------------------------------------------------------------- 547 LogOptions=00000000 00000001 547 ------------------------------------------------------------------- 547 ------ Setting the hooks and direct calls into the simulator ------ 547 --- CONTROLS timer memory location obtained ok 547 --- SIM1 Frictions access gained 547 --- FS Controls Table located ok 547 --- Installed Mouse Macro hooks ok. 547 --- Wind smoothing fix is fully installed 547 --- All links checked okay 547 ------------------------------------------------------------------- 547 SimConnect_Open succeeded: waiting to check version okay 547 Trying to use SimConnect Steam 2375 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 2375 Initialising SimConnect data requests now 2375 FSUIPC Menu entry added 2390 E:\Program Files (x86)\Steam\steamapps\common\FSX\flights\other\FLTSIM.FLT 2390 E:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air 7359 Weather Mode now = Theme 20172 E:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\VRS_FA-18E\FA-18E-6.8_SE.air 74203 System time = 05/09/2016 18:12:16, Simulator time = 07:11:05 (14:11Z) 74469 Aircraft="VX-9 "Vampires" CAG" 108969 Starting everything now ... 112328 Advanced Weather Interface Enabled 130125 Sim stopped: average frame rate for last 24 secs = 37.3 fps 130125 Max AI traffic was 33 aircraft 147031 Aircraft="VX-9 "Vampires" CAG" 280031 Sim stopped: average frame rate for last 111 secs = 41.4 fps 280031 Max AI traffic was 0 aircraft 315656 C:\Users\ptsar\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 328125 System time = 05/09/2016 18:16:30, Simulator time = 07:13:26 (14:13Z) 328125 *** FSUIPC log file being closed Minimum frame rate was 32.9 fps, Maximum was 66.9 fps Minimum available memory recorded was 2029Mb Average frame rate for running time of 138 secs = 40.8 fps Maximum AI traffic for session was 33 aircraft Memory managed: 80 Allocs, 80 Freed ********* FSUIPC Log file closed *********** Any ideas? I would love to be able to use this for controlling my VRS superbug thanks! Edited September 5, 2016 by Greekbull
Pete Dowson Posted September 6, 2016 Report Posted September 6, 2016 7 hours ago, Greekbull said: But when I go back in game none of the commands are working. Using the exact same aircraft? Obviously, if youchoose an aircraft which is not yet assigned to a profile, they won't be loaded. Normally it is best to do all your default assignments, calibrations, etc, without using a profile, then just create profiles for when you decide you need things done differently for different classes of aircraft. For 90% of users things aren't that complicated and profiles aren't needed or used. 7 hours ago, Greekbull said: I tried getting rid of the dll file Er, why? Removing FSUIPC will simply stop it loading so nothing will work! 7 hours ago, Greekbull said: and even deleting and reinstalling with the same result. Reinstalling the same software should do the same thing, as it won't change between installs, obviously? 7 hours ago, Greekbull said: Here's my log: The log is fine. The log is not the important thing here, it is your settings. Please show me the FSUIPC4.INI file, which is where they are stored. Do you disconnect and reconnect your joystick controls between sessions, or are they always left connected? Windows 8 and 10 both have the habit of losing or changing the joystick ID numbers if you do that. I suspect they may do it even if you do not disconnect/reconnect -- Win 7 was better in this area. Best to ask FSUIPC to use joystick letters for assignments so it can keep track. There's a chapter about that in the User Guide. 7 hours ago, Greekbull said: I would love to be able to use this for controlling my VRS superbug You never fly anything else? If so, why a Profile just for one aircraft? Note that if you normally want to fly a specific aircraft each time you load FS, you'd be better off (speedier loading,etc), saving your normal starting flight "as default". Currently you are loading FS with this flight: E:\Program Files (x86)\Steam\steamapps\common\FSX\flights\other\FLTSIM.FLT and this aircraft: E:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air That's the install default for FSX-SE. Best to save your own default, saves a lot of FS messing at the start. Pete
Greekbull Posted September 7, 2016 Author Report Posted September 7, 2016 Great thank you for the tips I got it working!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now