Search the Community
Showing results for tags 'profile'.
Found 2 results
Dear Pete, I have a registered copy of FSUIPC which I've been enjoying for some time. Yesterday I flew the A2A Piper Cherokee 180 in the latest ver of FSX SE with no issue. Tonight, some of my control assignments are not working. Let me elaborate. As a matter of course, I disable FSX controllers and use FSUIPC for direct axis assignment, buttons, macros etc. When I say 'some' assignments aren't working, an example would be: Throttle assigned direct axis through FSUIPC - Black Lever of a Saitek Pro Flight Yoke - worked before this problem started happening - worked after the problem started happening Mixture assigned direct axis through FSUIPC - Red Lever of a Saitek Pro Flight Yoke - worked before this problem started happening - suddenly FSUIPC GUI doesn't report this axis as assigned and the control does not respond in flight. Open Panel (Shift + 2) Assigned to button #15 of a Saitek Pro Flight Yoke - worked before the problem started happening - suddenly FSUIPC GUI doesn't report this button as assigned and the button has no affect in flight. So from my originally assigned controls, some still work, some don't. The steps I took to solve the issue were: Close FSX SE Inspect the FSUIPC4.ini, looking in the profile section, for the aircraft I was flying to see that the assignments I would expect, are there. In loading FSX SE back up again, it took longer than usual to load and chucked an error (below). My options were to continue loading FSX without FSUIPC or to continue. I chose continue and the FSX Fatal Error: Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a Faulting module name: FSUIPC4.dll, version: 184.108.40.206, time stamp: 0x58933f1b Exception code: 0xc0000005 Fault offset: 0x0001f145 Faulting process id: 0x1f8c Faulting application start time: 0x01d3b65e79e37e81 Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.dll Report Id: d6aefcec-2251-11e8-82ae-2cd05a9207f2 Faulting package full name: Faulting package-relative application ID: I then couldn't start FSX SE from then on without FSUIPC crashing. So I downloaded a fresh installer, and reinstalled FSUIPC and ensured, it was registered. Since, it's been okay in so far as it loads again without issue and no more errors. I still have the problem with the assigned controls on the PA-28. I then edited the FSUIPC4.ini file to remove the association of the specific PA-28 I fly from the profile. Specifically, I removed the last line in the code below: [Profile.Piper Cherokee 180] 1=Piper Cherokee 180 2=Piper Pa-28-180 Cherokee 5 For reference, from the aircraft CFG, I fly G-KELS [fltsim.5] title=Piper Pa-28-180 Cherokee 5 sim=PA28_180 model= panel= sound= texture=white-grey kb_checklists= kb_reference= atc_id=G-KELS ui_manufacturer="A2A Piper" ui_type="PA28-180 Cherokee" ui_variation="White-Grey" ui_typerole="Single Engine Prop" ui_createdby="A2A Simulations Inc." Any idea what would be preventing the axis and button assignments that I see in my FSUIPC4.ini file from being available (ie working) in FSX? I should also note other addons I have that may or may not be having an affect. I use EzDok (EZCA.exe), an older version because believe it or not, I found it to me the most stable but it does fill up my error logs, for a pastime. One of many examples: Faulting application name: EZCA.exe, version: 220.127.116.11, time stamp: 0x2a425e19 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0xff300000 Faulting process id: 0x1e74 Faulting application start time: 0x01d3b65e84452a69 Faulting application path: C:\Program Files (x86)\EZCA\EZCA.exe Faulting module path: unknown Report Id: c32c6c8c-2251-11e8-82ae-2cd05a9207f2 Faulting package full name: Faulting package-relative application ID: Thanks, PS. I read through your 'read this before posting a support question post' and hope I have sufficiently explained the issue and provided detail where possible. Also hope it's not something really daft :-0
Hi Guys, I am using FSUIPC 5 and today I installed the new FS2Crew for P3Dv4. As expected, I am running into problems unfortunately. So, after installing and configuring FS2Crew for P3Dv4, FSUIPC 5 is not keeping the profile saved for the same plane. Which means I have to select the profile each time I run the same plane. Any idea what or where the problem could be? Thanks in advance for your kind help and feedback. Kr, Enrico