qqwertz
-
Posts
33 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by qqwertz
-
-
Two days ago, I installed the PMDG 738 in MSFS (all latest software, FSUIPC7 7.3.19 on Windows 11). I now wanted, for the first time since that installation, make a flight with a different airplane (Kingair 350 analog by Blacksquare), which used to work fine until now. However, I can do what I want, FSUIPC always assigns the B738 profile to this airplane. I does not so this at least for several other airplanes.
I tried editing the FSUIPC.ini file (see attachment) and removed any reference to the KingAir, and deleted its profile. I moved the new 738 entries to a different location, so that it is not the last entry in FSUIPC7. I restarted MSFS and my computer, all in vain.
How can I get the KingAir to work again? Thanks for any help,
Peter
-
Hello John,
many thanks for your quick reply, and apologies for my belated response - life got in the way.
>> Also check that the buttons/switches you are using are not also assigned in MSFS.
I think that was exactly the problem. I cannot tell for sure since SU12 was installed today, but the switches were also assigned to flaps increase/decrease in the simulator. After I deleted that, flaps worked fine with FSUIPC. The airplanes where I encountered problems only have three flap positions. Hence, if both FSUIPC and the simulator increase flaps, I would go from up to down in one step.
Thanks a lot for your help, which likely has resolved my issues. I will report back in case I encounter more difficulties.
Cheers,
Peter
-
I have a strange problem: I have assigned flaps to one of the switches on my yoke. The assignment is done differently for different airplanes. Sometimes I map the switches as a key press (F6/F7), sometimes as an FS control (flap incr/decr). It is always mapped to an incremental increase or decrease, never to flaps full up or full down.
For the last few weeks, however, flaps go only to the full down or full up position, regardless how I made the assignment. Even worse, when I fly a plane without a profile-specific assignment, FSUIPC appears to block any change in flaps. I can then neither operate the flaps using my yoke, nor in the VC, nor via keyboard.
I discovered that the problem is resolved after I open the button/switches assignment page and click on "reload all buttons". After that, flaps work with incremental increase again. However, I have to do that every time I start my simulator.
I only understood that this is a FSUIPC problem now, but in hindsight I can tell that this started some time during the last 2-3 weeks. Any help would be greatly appreciated.
Thanks,
Peter
-
Hello John,
thanks a lot, that general advice to use logging did the trick. Helicopter controls seem to be a bit special in the sim, but I got it to work as I wanted 🙂
Cheers,
Peter
-
I am trying to assign an axis for throttle in the new default helicopters in MSFS, but I cannot get it to work. I am using the latest version of FSUIPC7, and I use "helicopter throttle axis" in FSUIPC7. The axis of my TQ6+ is found and assigned in FSUIPC7, but it just doesn't do anything in the game.
Almost all other axes assignments with FSUIPC work just fine. Only the condition lever in turboprops doesn't work either (since SU10, I think), but I was OK with setting that in the VC. The throttle is a different matter, though.
Thanks for any help you may offer,
Peter
-
Thanks so much for your continued support of the flightsim community. I will get FSUIPC5 as soon as you will release it.
Peter
-
I finally got it to work by deleting FSUIPC.ini and removing all my FSUIPC settings. I am not sure if I can use FSUIPC axis assignments with other planes, so far all planes that I tested worked with the new approach that does not involve FSUIPC. I will report if I run into a problem with other planes because of this change.
Peter
-
I am now certain that on my system the problems are caused by the new PMDG 747:
- After a flight with the 747, P3D will not restart unless I reinstall FSUIPC. If I do, everything works (mostly, see below) fine.
- If I do not use the 747, then P3D is able to restart without reinstalling FSUIPC
- PMDG discourages the use of FSUIPC for calibrating yokes etc in the manual
- There is a bug in the autopilot of the 747 when FSUIPC is used. The AP always disconnects after a few seconds unless a certain option in the PMDG setup is changed, see http://www.avsim.com/topic/503044-747-v3-autopilot-issue/
- Engine performance is ridiculously bad with FSUIPC enabled: http://www.avsim.com/topic/503546-flight-dynamicsweight-and-balance-issue/
Peter
-
I should have made one more test :)
P3D didn't start again, but did so after reinstalling FSUIPC. It seems that for now I have to reinstall it every time before launching P3D
Peter
-
Hello Pete,
It looks like you are on the right track regarding PMDG planes. I was able to resolve the problem doing the following.
- I uninstalled the new PMDG 747. This didn't change anything at first
- I disabled all dll modules in dll.xml . P3D then started normally
- I re-enabled first FSUIPC and then subsequently all other modules. P3D was able to get to the start-up screen after each change.
- I then launched the default flight with success. Except that the FSUIPC menu and functionalities were gone (with the module being enabled)
-I re-installed FSUIPC. After that it was working fine again.
- I re-installed the 747. When I only started a flight with it there were no problems after restarting, but after I initialized the plane to cold & dark and restarted P3D, the problem reappeared.
- After that, I set SavePreviousFlight=No in FSUIPC.ini, but it didn't help. By the way, RAAS remained disabled during these procedures.
- Re-installing FSUIPC fixed the problem.
This long list is simply an accountof my trial and error session. I would guess the essential elements are to re-install FSUIPC and to add SavePreviousFlight=No in FSUIPC.ini .
I will let you know if the issue occurs again.
Thanks and best regards,
Peter
-
Hello Pete,
sorry, I forgot to mention that; I have read the posts about restarting P3D and tried to eliminate this possibility.
- I restarted my computer and did nothing but starting P3D, but even then I get the same problem.
-I do not have the files "Previous Flight.wx" and "Previous Flight.fxml" in C:\Users\username\Documents\Prepar3D v3 Files\ (and that directory is the one used by P3D for the error log), nor anywhere else, possibly because I am using AS16. I also tried to delete the AS16 weather files (activeflightplanwx.txt, current_wx_snapshot.txt, LastDownloaded.Wx), but it had no effect.
- I always launch P3D with the default airplane (F35) at the default airport, with the start-up screen enabled.
- I am using the registered version of FSUIPC under Win 10.
Thanks for looking into this,
Peter
-
On 2/2/2017 at 1:24 PM, Vashq8 said:
After some testing, I found the problem maybe is laying in "Previous Flight.wx" and "Previous Flight.fxml". After exiting the simulator I simply delete both files and P3D would start fine. If I leave the files P3D would crash again.
Same problem here. With FSUIPC enabled, P3D 3.4 HF3 hangs (the startup window closes but the program is still running in the task manager and consuming CPU resources). With FSUIPC disabled iP3D starts just fine. I have installed the most recent versions of FSUIPC, P3D and Simconnect. I don't use RAAS and I didn't find "Previous Flight.wx" and "Previous Flight.fxml" anywhere (except very old ones in my FSX folders).
Sometimes the Windows Event Viewer shows an error message, sometimes it shows nothing.
Peter
-
Hi Thomas,
thanks a lot for your help. The last 2-3 attempts on my system were successful, so I will wait with deleting the weather stations until the problem occurs again (and then I would send the logs). I did check the logs and they refer to 4.959.
Thanks,
Peter
-
I have the same problem: The latest version of P3D 3.4 together with the latest (registered) version of FSUIPC will result in the simulator not getting to the initial screen where you can elect vehicles, flight plans etc. Here are a few more details.
- I have added ManualLoad = True to the dll.xml file. P3D 3.4 works fine if I do not load FSUIPC, but it normally (not always) "crashes" if I do.
- P3D is not really closing. It is still visible in the Windows Task manager and draws significant system resources (CPU load about 25%). I have to stop P3D manually there.
- A fresh install of FSUIPC using the latest installer usually helps for the first 1-2 runs. After that, P3D fails to launch again.
- Here is my Windows event viewer log:
Faulting application name: Prepar3D.exe, version: 3.4.18.19475, time stamp: 0x5851bfd2
Faulting module name: FSUIPC4.dll_unloaded, version: 4.9.5.8, time stamp: 0x5857240f
Exception code: 0xc0000005
Fault offset: 0x00067797
Faulting process id: 0x3168
Faulting application start time: 0x01d25ef2fd44e6d1
Faulting application path: D:\P3D-3.0\Prepar3D.exe
Faulting module path: FSUIPC4.dll
Report Id: 457a7181-a525-44aa-941d-d2f3059eefa0
Faulting package full name:
Faulting package-relative application ID:- You may notice that it states version 4.9.5.8, and this may be at the heart of the problem. I have re-downloaded the 4.9.5.9 installer multiple times, and it does contain the list of 4.9.5.9 changes. However, it appears to install version 4.9.5.8 of FSUIPC.dll
Thanks and best regards,
Peter
-
Hi Pete,
thanks a lot for your reply, which helped me to get on the right track. This morning I completed a long flight without the wheel and everything worked fine. I then installed a driver update for the wheel and was able to calibrate it using FSUIPC. Previously it only showed up under "axis assignment" in FSUIPC, not under "Joystick calibration".
I will now do a test flight, hopefully the new driver resolves all issues. If not I will report back.
Thanks and best regards,
Peter
-
Hi,
I also have issues with this trim wheel. FSUIPC (registered latest version) lets me assign the device (elevator trim) and the wheel works. However, when I try to calibrate the wheel in the corresponding section of FSUIPC, the axis is never detected. Also, changing any settings (e.g., reverse operation) has no effect.
When I say "the wheel works" that is actually only sort of true. It appears that often the wheel is only recognized after I move it. I then hear the Windows 8 "USB device unplugged" sound, followed by the "USB device detected" sound. Only after this procedure the wheel works.
I am not sure if this is related, but since about the time when I got the wheel (two months ago) I have issues with all my USB controls. On long flights (typically with PMDG planes) yoke, trim wheel and throttle quadrant (all Saitek) disconnect in mid flight. Other USB devices are not affected. I didn't have these issues before as long as I used FSUIPC to connected the controls. I have made sure that no buttons etc of any of the controls are assigned in FSX.
In my FSUIPC log file, the message
15674641 ***** HID USB device reconnected: re-initialising FSUIPC connections
is frequently repeated after the controls are disconnected.
Any help or suggestion would be greatly appreciated.
Thanks and best regards,
Peter
-
Thanks Pete,
that solved my problems.
Cheers,
Peter
-
Hi Pete,
wow, you're fast. Thanks for replying so quickly.
I still suggest you test with FSX controllers actually disabled.Ooops. I thought you meant removing all button assignments, I never realized that you actually could disable the controllers completely in FSX :oops:
I just did that and the double assignment is indeed fixed. However, it appears I can only disable all controllers together. I therefore also lost the mouse controls, which I use very often to change the view (with the space bar held down). Is there a way to disable individual controllers or to use FSUIPC to get this back (I tried to assign "mouse look" and "mouselook" but it didn't work)?
Thanks,
Peter
-
Did you disable controllers in FSX?
Hi Pete,
yes, I made sure that under FSX settings all button (and axis) assignments for the Saitek yoke are deleted, both in normal and in slew mode. I verified that there were no assignments even after several restarts of FSX. I never installed the Saitek software.
I have a double assignment for Aileron trim right / gear toggle and elevator trim / flaps. All other assignments work perfectly. In the log file these events look as follows:
158157 Button changed: bRef=0, Joy=0, Btn=7, Pressed
158157 [buttons] 22=R0,7,C66277,0
158157 Repeating flag set: bRef=0, Joy=0, Btn=7 (RepeatDelayCtr=1)
158157 FS Control Sent: Ctrl=66277, Param=0
158157 *** EVENT: Cntrl= 66277 (0x000102e5), Param= 0 (0x00000000) AILERON_TRIM_RIGHT
158157 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE
152610 Button changed: bRef=0, Joy=0, Btn=4, Pressed
152610 [buttons] 6=R0,4,C65607,0
152610 Repeating flag set: bRef=0, Joy=0, Btn=4 (RepeatDelayCtr=1)
152610 FS Control Sent: Ctrl=65607, Param=0
152610 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN
152610 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR
The corresponding settings in FSUIPC.ini are
6=R0,4,C65607,0
22=R0,7,C66277,0
Thanks for looking into this,
Peter
-
I definitely did not drink too much Bruichladdich, but I have the same problem: under Win 8 I assigned some buttons on my Saitek yoke via FSUIPC (registered) for trim. However, these buttons also raise/lower the gear and flaps, even though I was careful to delete all button assignments (both in normal and slew mode) for the yoke in FSX itself.
If that may have something to do with it: my default flight is for the Majestic Dash 8.
Thanks,
Peter
-
Hi Pete,
thanks for the link. Indeed the original link I included wasn't working anymore. I have changed it to your link, the binaries from both sources are identical.
Cheers,
Peter
-
This is a little LUA script to have checklists displayed item by item in FSX and also having it spoken by a text-to-voice program. The script recognizes the plane and loads the corresponding checklist. Sound can be switched on or off. Currently PMDG Jetstream 41, Beechcraft 1900D and 737 900NGX as well as RealAir Beech Turbine Duke and Wilco CRJ 700 NG are recognized. You can download the script at
-
Hi Pete and Paul,
wow, you are fast, thanks a lot for the very quick response. I tried it and it worked like a charm.
I just bought the FSUIPC registration last Saturday because I never really understood why I would need it.
Now I can't see how I could live without it, FSUIPC really opens another world. Thanks for this awesome
program, Pete.
Peter
-
Hi,
I am new to LUA and have two rather basic questions.
1) I am trying to set up a function that is called when Shift-H is pressed, i.e., something like
event.key(72, 1, "functionName")
This works fine when I call it the first time, but it doesn't call the function when I press Shift-H again. Only if I hold Shift-H for a while and then press Shift-H once again the function will be called again.
I also tried to set a downup parameter but received the same result. Is there any way to avoid having to hold Shift-H ?
2) I want to program a function that recognizes the airplane in use. Currently I am using ipc.getLvarId
and test if a local variable that can be associated with a specific plane is not nil. For instance,
I can recognize the PMDG JS 4100 through
if ipc.getLvarId("ConspicLight") ~= nil
This works but is rather complicated because I first have to find a variable specific for that plane. Is there a way to read the airplane name in LUA?
Thanks,
Peter
Axes assignments stuck with PMDG 738
in FSUIPC7 MSFS
Posted
That is probably it. I have a RCAF livery for exactly these two airplanes, and the 738 livery from flightsim.to only had texture files, no proper directory structure. I just called it RCAF, and that will likely interfere with my KingAir.
I'll try it out and will let you know if the problem persists.
Thanks a lot, John.
Peter