seiermax

OOPS - my contribution was posted befoer I was ready - sorry for that: So again 1) Under the KeyPresses register set a key combination (e.g. Tab+Ö) 2) Select as contol sent when keys pressed: "Aileron Trim Set" (or Elevator/Rudder Trim Set) 3) Add as parameter for the key press some small value, e.g. 1 4) Select the same control as in step 2) (i.e. "Aileron Trim Set") also for the control sent when main key released 5) Set the parameter for the main key release: 0 (i.e. center the trim) 6) Confirm the selection of this key combination as usual. Now if you want to center the trim, you just press and release button combination. When you release it, your trim will be centered, and thats what you probably want to happen. Theoretically there is a little notch in the trim when pressing the key combination but you wont notice that. It works stable, also when you repeat it several times. Whether you change the trim by a joystick button or with the mouse doesnt matter. I checked it with the standard FSX Beech Baron 58 for elevator, rudder and aileron trim with the latest FSUIPC4 version 4.938f. Thaths how it looks like in the .ini-file: [Keys] 2=192,24,65706,1,65706,0 4=222,24,66731,1,66731,0 6=191,24,66732,1,66732,0 (P.S.: Dont bother with the 192, 222 and 191 keys, they are those "Kraut" umlaut-keys Ä, Ö and the # on my German keyboard) Maybe that helps someone who comes up with the same problem

Just an addititonal remark (I just fiddled around with the same problem): If you want to center rudder, aileron and elevator trim by a keystroke with FSUIPC4 (I have the Acceleration Pack, not the Steam Edition, but thats probably not the issue), and if you dont want to go into Macro programming: -

When installing FSFlyingSchool2015 I noticed again a small problem which has been around there for quite some time: If you have installed MakeRwys.exe V4.675 it is replaced without warning by the older V4.4.1 whenever you update your runways for FSFlyingSchool :huh:. The solution is easy (copy latest version into both the FSX folder and the FSFlyingSchool folder), but a little of a nuisance. I couldnt find any problems for FSFlyingSchool with V4.675 which is surely around for whatever good reasons. I just made a post to this issue in the FSFlyingSchool forum, but wanted to pass on this information here to all FSX pilots who use both the MakeRwys and the FSFlyingSchool program: Check if you still have the latest MakeRwys on your computer! Merry Christmas and a Happy New Year to all!

Wow, thats a quick Response! TY again Max

Stupid question maybe, but anyhow: Just updated on FSUIPC Version 4.936. In the change descirption sheet ("FSUIPC 4.936 changes since 4.92") there is a remark under number 8 which refers to a separate document: Quote:; "... please see the separate document about this entitled "Profiles in Separate FIles" (end of Quote) Now i tried all kinds of places to look for this document, but in vain. Maybe i have tomatoes on my eyses or something like that. But: Could someone please give me a hint where i can find it? Thanks a lot in advance, Max

Greetings, Pete, seems to me that the problem is fixed. Just tried it out with version 4.646 and made the following experiments a) new dll 4.656 and no ini file at all: -> FSX started without any problems and created a new ini file B) new dll 4.646, but replaced ini file with previous ini-file, which had originally given problems with 4.645, but worked after several tries -> FSX started normally too without problems c) old dll 4.645 and an ini file which gave problems earlier -> problem with 4.645 showed up as usual -> killed FSX by means of the Windows task manager -> replaced old dll with new 4.646 dll, but left the ini as it was -> With 4.646 FSX started without any problems The Sound Section of the ini file after this test came out as: [sounds] Path=C:\Programme\Microsoft Games\Microsoft Flight Simulator X\Sound\ Device1=Primärer Soundtreiber Device2=Realtek HD Audio output So I think the problem is solved with version 4.646. If it should show up again, I will send you the relevant data immediately. Thank You for your efforts and your patience with a newbie... Best regards, Max P.S. Let me guess: Was it the German "umlaut" ä in "Primärer " which gave the troubles?

Greetings, Pete, just a quick answer (have to leave for work soon). I have added the 2 lines to the General section as you mentioned. "Experiment 1" Error message reproduced, after several tries started FSX without FSUIPC (pressing the "no" key) Sound Section of ini file: [sounds] Path=C:\Programme\Microsoft Games\Microsoft Flight Simulator X\Sound\ Those are the 2 last lines in the INI file. Corresponding log file: ********* FSUIPC4, Version 4.645 by Pete Dowson ********* Reading options from "C:\Programme\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... User Name="Max Seiermann" User Addr="seiermax@t-online.de" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=15 78 System time = 04/01/2011 08:11:02 78 FLT path = "C:\Dokumente und Einstellungen\admin\Eigene Dateien\Flight Simulator X-Dateien\" 78 FS path = "C:\Programme\Microsoft Games\Microsoft Flight Simulator X\" 672 LogOptions=00000000 00000211 672 Sound: Path=C:\Programme\Microsoft Games\Microsoft Flight Simulator X\Sound\ 672 Sound: EnumDevice=Primärer Soundtreiber -----End of log file "Experiment 2" Error Message came, but tried to load FSX with FSUIPC anyhow (pressing the Yes key). FSX now accepted FSUIPC on the 1st try (normaly it took many more tries...) Sound section of ini file is now: [sounds] Path=C:\Programme\Microsoft Games\Microsoft Flight Simulator X\Sound\ Device1=Primärer Soundtreiber Device2=Realtek HD Audio output ----- end of sound section, but ini file continues with [JoystickCalibration] The corresponding log file: ********* FSUIPC4, Version 4.645 by Pete Dowson ********* Reading options from "C:\Programme\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... User Name="Max Seiermann" User Addr="seiermax@t-online.de" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=15 94 System time = 04/01/2011 08:20:07 94 FLT path = "C:\Dokumente und Einstellungen\admin\Eigene Dateien\Flight Simulator X-Dateien\" 94 FS path = "C:\Programme\Microsoft Games\Microsoft Flight Simulator X\" 688 LogOptions=00000000 00000211 688 Sound: Path=C:\Programme\Microsoft Games\Microsoft Flight Simulator X\Sound\ 688 SimConnect_Open succeeded: waiting to check version okay 3079 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 3079 Initialising SimConnect data requests now 3079 FSUIPC Menu entry added 3125 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 3125 c:\dokumente und einstellungen\admin\eigene dateien\flight simulator x-dateien\EDNR.FLT 3125 C:\Programme\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR 28110 Weather Mode now = Theme 141985 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 142032 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 142969 System time = 04/01/2011 08:22:30, Simulator time = 08:20:36 (07:20Z) 142969 Aircraft="Cessna Skyhawk 172SP Paint1" 143297 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2395, Index param -1 on Weather request type 5 145297 Advanced Weather Interface Enabled 147297 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2398, Index param -1 on Weather request type 5 158922 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 164032 System time = 04/01/2011 08:22:51, Simulator time = 08:20:51 (07:20Z) 164032 *** FSUIPC log file being closed Average frame rate for running time of 17 secs = 113.4 fps Memory managed: 8 Allocs, 8 Freed ********* FSUIPC Log file closed *********** Hope the information above is useful to you. Just feel free to let me know if I can give you further informations. Regards, Max

Greetings, Pete, now I managed to reproduce the problem. Maybe therefore the following information might be of interest for you. The FSX messages were as follows (translated from German, have to type them manually, as the screenshots are > 20K and I cant attach them): 1) The message which says "Flight Simulator has found a Problem with a 3d-party software (add-on)" has the parameters: Name: FSUIPC4DLL: FS new universal IPC interface Version: 4.645 Company: Peter L. Dowson File: Modules\FSUIPC4.dll It continues with the option to execute this softare (Yes and No buttons) 2) After pressing Yes in the above message, a new message shows up which gives the option to send a problem report to Microsoft. This report would contain the following data Exception Information: Code: 0xc0000 Flags: 0x00000000 Record: 0x0000000000000000 Address: 0x00000000610561b5 System Information Windows NT 5.1 Build: 2600 CPU Vendor Code: 756E6547 - 49656E69 - 6C65746E CPU Version: 000006FB CPU Feature Code: BFEBFBFF Module 1 fsx.exe Image Base: 0x01000000 Image Size: 0x00000000 Checksum: 0x002ab03c Time Stamp: 0x46fadb14 Version Information The following files will be incorporatet into the error report: C:\Dokumente und Einstellungen\admin\Anwendungsdaten\Microsoft\FSX\fsx.CFG.txt (path is in German, in English I think it would be something like ...documents and settings\username\application data\..., this is the complete path to my FSX installation) ...\FSX\dxdiag.txt ... \FSX\scenery.cfg ...\FSX\fdr.dat ...\FSX\DLL.xml I tried to attach the FSUIPC log file to this reply, but the system tells me that I am not allowed to do it. So I just copy the contents: ********* FSUIPC4, Version 4.645 by Pete Dowson ********* Reading options from "C:\Programme\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... User Name="Max Seiermann" User Addr="seiermax@t-online.de" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=15 78 System time = 02/01/2011 20:04:18 78 FLT path = "C:\Dokumente und Einstellungen\admin\Eigene Dateien\Flight Simulator X-Dateien\" 78 FS path = "C:\Programme\Microsoft Games\Microsoft Flight Simulator X\" 657 LogOptions=00000000 00000001 (end of log file) Again: No need for me that you bother about that problem too much, i can live with this situation. But maybe the information above is useful for you in general. Feel free to let me know whether I should save some files or get some other data out of my system to you if the problem happens again. Thanks again for your time, Max

Greetings, Pete, Thank You for your quick answer. This information was on a pdf file which I attached to my original posting. Seems this file didnt go through. As it works now, the original log file has been overwritten. Unfortunately I didn't keep a copy of the old log file. I just wanted to know if someone by chance knew a more efficient way than starting FSX again and again for some 15 minutes or so until it finally works. Sorry to have bothered you, Max

Hi all, like goo in his topic from Dec. 25, I get a fatal error too. However I use the latest update 4.645. With 4.60 this never happened. My FS is the German version with the acceleration pack The symptoms are the same, when loading FS it says that it has a problem with FSUIPC4.DLL, version 4.645 and recommends not to execute it. If this recommendation is ignored, it proposes to send an error report to Microsoft. See attached screenshots (unfortunately in German). The problem happens - when I for the first time started FS after installing version 4.645 - whenever i exchange the FSUIPC4.ini file (i.e. delete it and copy an earlier version into the system). After several tries it finally works, and then I cant detect any more malfunctions. However I couldnt find out the exact mechanism what makes it work (how often to select what options offered on the screen etc...). So this is rather frustrating..... Does anyone have an idea how to fix this problem, or at least how to make FS accept the dll in a straightforward manner? Thank You in advance for any good ideas!