Jump to content
The simFlight Network Forums

Alhard Horstmann

Members
  • Posts

    170
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Alhard Horstmann

  1. ....., then maybe your method makes more sense. I don't know from what you describe.

    Regards

    Pete

    Yes, my profile affects also other things than game controllers, eg.: wind, visibility, clouds, battery life and a lot of parameters in FS9/FSX CFG.

    Pete, please clarify, due to my not very experienced english I do not understand your last sentence: "I don't know from what you describe". Is this another question to me??

    regards

    Alhard

  2. This will be in 4.627 which I'll upload to the Updates announcement either tonight or more likely some time tomorrow (Tuesday).

    Regards

    Pete

    Hi Pete, that solution for FSX is great! Thanks. I installed it immediately, see picture.

    And I owe you an explanation why I need these different INIfiles:

    I am flying with a lot of different, let's say "MyProfiles". That is e.g. flying jets, helis, propellers and cars ( :) ). in different conditions: VFR, IFR, bad weather, good weather, realistic, NOT realistic (for kids). Additional I am using test versions for all these "MyProfiles".

    I start all this with different icons on my desktop. Below these icons I put links to the associated FS.CFG + FSUIPC.INI, so I can jump directly into the configuration files of a specific "MyProfile" (see second picture) for editing the configuration.

    Your FSUIPC feature "User profiles for all control settings" is very helpful for different aircrafts but not for different profiles as I described above.

    Does this answer your question about my requirements? Or did I misunderstand the usage of your "Profiles" feature?

    best regards

    Alhard

    post-26245-128689723192_thumb.jpg

    post-26245-128689723198_thumb.jpg

  3. Thanks Pete, here the reason for my post:

    I want to identify in FSX UI what version of FSUIPC4.INI I am using actually. I did that in FS9 by editing the SubMenu entry (e.g.: SubMenu=&mein Heli FSUIPC 100806 for my helicopter INI file).

    Now I have an idea: Isn't it possible that you provide a user defined text line in your main "FSUIPC Option and Settings" window. This text line will be filled by an entry in FSUIPC4.INI.

    What do you think?

    best regards

    Alhard

  4. I've installed FSConnect.dll into my own FS9 installation, and FSUIPC 3.989 still loads fine. So it isn't simply the installation of FSConnect which creates the problem (assuming you are also use version 3.00 for FSConnect.dll?).

    So it seems I will know what it is being used for, on your system, and work out some way to re-create the same conditions here.

    Yes, it is V 3.0 of FSConnect. Will you recreate the conditions before your holidays? I would prefer to help you after your holidays, cause I am busy tomorrow and on Wednesday. In the meantime i will make some tests using procmon and filemon.

    BTW: have you heard anything from "alvarado" ?

    regards

    Alhard

  5. Hi Pete, I FOUND THE EVIL-DOER !!! It was FSConnect.dll by Russel Dirks.

    Now shortly back to the last anwers:

    As I wrote before, the message comes BEFORE a new FS9.CFG was created.

    I don't understand. Are you deleting the FS9.CFG before starting FS9?

    Yes, I deleted the CFG before.

    There is one thing you can check, please. Delete or rename the FSUIPC.INI file before starting FS9, with 3.989 installed. After it is rejected by FS, see if there is an INI file produced. If so, show it to me please. It might tell me how far it got.

    There was no new INI file created.

    [LATER EDIT]

    Another thing that occurs to me is that, if it is getting clobbered so early it is unlikely to be the fault of any add-on which isn't part of what gets loaded very early on, like FSUIPC. For that to happen it must either be whatever aircraft you have loading initially (and I think that was a default FS aircraft, wasn't it, so would be okay), or, much more likely, another DLL installed in your FS Modules folder.

    So, could you compare the DLL's listed in your new "virgin" FS installation with those in your original installation, and tell me what ones are extra, apart from FSUIPC.DLL.

    THIS WAS THE MOST IMPORTANT ADVISE !!

    I compared and I had 14 additional DLLs. I deleted all and moved it back one by one with intermediate test of FS.

    "FSConnect.dll" was then identified. I don't know what addon installed this DLL. I will find later.

    Now many thanks and enjoy you holidays.

    best regards

    Alhard

    PS: I hope the originator of this thread "alvarado" is now solving his problem also. Good luck!

  6. You can't? What on Earth is stopping you. Don't you read my messages? I said:

    1. Try swapping the DLL with the latest increment from the Updates announcement above.

    Sorry Pete, I understand that you are angry about me and you are right: I am confused. But now I am cleared, (I hope :D ).

    I always looked on the schiratti.com site and did not realize that there is a page "Updates and other goodies" in this forum. I was prejudiced reading your advice. Sorry. Until this week I never had problems with your product ( I even made presentations about FSUIPC) so I never needed to go to this forum.

    Back to our Problem: nothing is solved. I copied your interim version 3.989 in the modules folder --> no positive result -same error message.

    As I wrote before, the message comes BEFORE a new FS9.CFG was created.

    Do you know a good process tracker ?

    The other way it do adopt a process of elimination, to see what is going on. If you stick to an old version of FSUIPC please never ask for any further support.

    Yes, now I am going the process of elimination. I never would ask for support for an old version. I was software developer, I know this.

    Did you retry 3.98 on your original configuration after installing the fresh copy of FS elsewhere?

    Yes, I did it on a new partition with a complete new FS9 installation, and it WORKED !

    If the problem was due to some file missing or incorrect which is installed in a common area then just installing another FS might have fixed it in any case. Otherwise, you can use your fresh installed copy as a source of replacement files for your old installation -- i.e. perform a sort of merge. There are many ways to isolate and correct the problem, but it might take patience and time. This is the way with any sort of corruption in a large installation I'm afraid.

    I will do that, but do you have any idea what change in your V3.98 DLL could lead to this behaviour. It must be in the first steps FS is running in. You know my system runs with V3.93 and I did not change anything before updating on V3.98. It still runs with V3.93.

    No, that is not true I'm afraid, because FSUIPC is not actually running, and there would be a slight difference in memory arrangements in every single increment -- obviously, as if everything were identical it wouldn't be a different version. I know what I've changed in each version, and none of it applies to anything in FSUIPC before it starts the Log file..

    That is really strange. But now we have isolated a small time slot of the involved processes.

    I need a process tracker utility.

    Pete, thank you for your extraordinary patience with me and apologise that I sometimes have problems in understanding the English language.

    WE WILL FIND THE BUG!

    regards

    Alhard

  7. Try changing whatever you use for the default startup flight (change airport), it may be corrupted, also change to the default C172 as well. If that doesn't help backup then delete the FS9.cfg and let FS create a new one the next time it starts.

    I did that already. Thanks for the advise. As I wrote before I started with no FS9.CFG.

    But why do you think something is corrupted when everything runs until this Version 3.98 ???

    The error messsage comes BEFORE a new FS9.CFG is created !! I think that means, that the FS9.CFG has no impact on this error.

    By the way, I am flying with 3 different and individual configured FS9.CFGs. That was a lot of work and experience. Why should I start from the scratch simply due to a new FSUIPC update??

    Let us find the real reason together. I have to look for a good process tracker. Like the IP sniffer or "Filemon". Do you know one?

    Regards

    Alhard

  8. Is the description of the error there the same as the English from FS? Seems there's no other explanation anywhere?

    The description reads: "Flight simulator was unable to load some aircraft or software. You can contnue using Flight Simulator "

    No other explanation anywhere. I will try to use a process tracker to get more information.

    Then I installed a complete new XP with a new native installed FS9. No Add-Ons, nothing extra!

    There I installed afterwards FSUIPC V3.98.

    Result ==> NO ERROR !!

    That was rather extreme. Did you not even bother to try the current release, 3.988, first, as I advised? I don't understand why you won't try the things I suggest. :-(

    I do not have any 3.988. My DLL property says my downloaded version is 3.98.0 and your install log says version 3.98a ????

    I would try what you suggest, but can't.

    It is likely to have been some sort of corruption in the FS installation. I'd just install your favourite add-ons, but check after each install. This is good practice in any case -- never install more than one thing at a time without checking in between.

    Unfortunately this way would last many many days. I installed Gigabytes of sceneries, airports, aircrafts. I think I will fly with V3.93 furtheron :(

    It would help, if you send me the previous version 3.97.

    Why do you think that? There was no 3.97 in any case -- the previous main release was 3.96, and there were about 15 incremental releases in between. And in any case, how would it possibly help? What would you learn?

    I could check from what version on you made changes in your DLL and you could think of potential triggers (memory change??) for the faulty behaviour in that release.

    regards

    Alhard

  9. Pete, I am so sorry not to be precise enough and I have forgotten to add some needed information. Please forgive me.

    Here is my response part 2:

    Case 1: FSUIPC is working with V3.93:

    Here is the logfile:

    ********* FSUIPC, Version 3.93 by Pete Dowson *********

    Running on Windows Version 5.1 Build 2600 Service Pack 2

    Verifying Certificate for "Y:\FS9\MODULES\FSUIPC.DLL" now ...

    SUCCESS! Signature verifies okay!

    Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

    User Name="xxxxxx"

    User Addr="xxxxxxx"

    FSUIPC Key is provided

    WideFS Key is provided

    Module base=61000000

    ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

    WeatherOptions(Orig)=40003605[40003605]

    InitDelay: 0 seconds

    WeatherReadInterval=4

    LogOptions=00000001

    DebugStatus=255

    593 System time = 16/06/2010 16:53:05

    593 \\...\y\FS9\

    593 System time = 16/06/2010 16:53:05, FS2004 time = 12:00:00 (00:00Z)

    1547 FLIGHTS\OTHER\FLTSIM.flt

    1593 AIRCRAFT\c172\Cessna172SP.air

    1593 Aircraft="Cessna Skyhawk 172SP"

    51343 \\...\c\Dokumente und Einstellungen\xxx\Eigene Dateien\Flight Simulator-Dateien\F0_EDDN Cessna cold P81.flt

    51375 Aircraft="Cessna Skyhawk 172SP Paint2"

    51625 Clear All Weather requested: external weather discarded

    52578 Advanced Weather Interface Enabled

    63078 Traffic File #14 = "scenery\world\scenery\traffic030528"

    63093 Traffic File #15 = "addon scenery\edde_erfurt_2008_v3.1\scenery\traffic_edde"

    121953 System time = 16/06/2010 16:55:06, FS2004 time = 15:05:02 (13:05Z)

    121953 *** FSUIPC log file being closed

    Memory managed: 0 Allocs, 396 Freed

    ********* FSUIPC Log file closed ***********

    Case 2: I swapped to V3.98:

    Sequence see attachment

    NO LOGFILE !! Really !!

    Event Viewer: Applikation -- Nothing

    System -- see attachment

    Then I installed a complete new XP with a new native installed FS9. No Add-Ons, nothing extra!

    There I installed afterwards FSUIPC V3.98.

    Result ==> NO ERROR !!

    That means, if you couldn't help me any more, I have to look for my FS9 Add-Ons which might produce this failure.

    My last installation was the DODOSIM Bell Helicopter.

    It would help, if you send me the previous version 3.97.

    I keep you informed.

    Regards

    Alhard

    post-26245-128689718147_thumb.jpg

    post-26245-128689718163_thumb.jpg

    post-26245-128689718176_thumb.jpg

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.