Problem with FSUIPC 3.999s

[scottmiller]

Recently I downloaded this version and immediately ran into problems with it. The first was the fact that it came with an installer which did not ask if I wanted it installed in FS98, FS2002, FS2004, and CFS1 and 2. As soon as I launched the installer it installed this version into all of the above. Why it installed PSUIPC in CFS1 and 2, when neither use it, is a mystery to me. I would REALLY prefer to install FSUIPC manually because of the following problems with trying to run it in any previous version of FS to FS2004...

FSUIPC 3.999s (why not simply round it up to 4.0?) ran fine only on FS2004....

Contrary to what Pete's website states this version does NOT work in either FS98 or FS2002 (at least not on my system). I didn't discover this until a couple of days later when I loaded a new aircraft in FS2002. The plane appeared ok but when I switched to the cockpit view I found myself looking at the pilots seat instead of the 2D instrument panel. Coulcn't switch to the panel view or any other cockpit view. When I pressed S to go to the VC panel view, instead of getting the VC panel I got a panelless exterior view which spun wildly, non-stop, in the vertical. Pessing S again got me to the normal tower view then back to the unswitchable cockpit rear view....Restoring FSUIPC 3.90 from a backup got FS2002 back to normal.

I then tried running FS98, which I still have on my system (you don't just dump an classic just because a new version comes out, at least not in this case)! It crashed immediately. After I restored FSUIPC 3.70 from a backup FS98 was back to normal.

Even though this version did seem to work ok in FS2004, I restored verion 3.98a to FS2004 as well. While I was at it, I upgraded FS2002 to this version and it seems to work fine. I tried upgrading FS98 to 3.98a but it cashed right after I click on "Fly Now"! Same thing with 3.90. Only FSUIPC 3.70 seems to work with FS98 properly unless something in the FSUIPC.ini file needs to be adjusted so versions later that 3.70 work with it (though is there any real need to update FS98 to a newer version of FSUIPC?). Diito when it comes to getting FSUIPC 3.999 to work with FS2002...

Unless someone can tell me how to get 3.999s to work in FS2002, I think I'll just stick with FSUIPC 3.98a for FS2002 and FS2004. Can anyone tell me where I can get a full installation copy of FSUIPC 3.98a (it was installed in FS2004 when I installed either PMDG's B747-400 or Quality Wings B757...)?

[Pete Dowson]

Recently I downloaded this version and immediately ran into problems with it. The first was the fact that it came with an installer which did not ask if I wanted it installed in FS98, FS2002, FS2004, and CFS1 and 2. As soon as I launched the installer it installed this version into all of the above. Why it installed PSUIPC in CFS1 and 2, when neither use it, is a mystery to me.

But it does work in both CFS1 and 2. It was only CFS3 where it was not possible. Your previous version must have been many years out of date becayse FSUIPC3 has come with an automatic installer now for about 5 years or so.

FSUIPC 3.999s (why not simply round it up to 4.0?

Not possible, version 4 is for FSX and later only. It would cause many application programs to fail.

Contrary to what Pete's website states this version does NOT work in either FS98 or FS2002 (at least not on my system). I didn't discover this until a couple of days later when I loaded a new aircraft in FS2002. The plane appeared ok but when I switched to the cockpit view I found myself looking at the pilots seat instead of the 2D instrument panel. Coulcn't switch to the panel view or any other cockpit view. When I pressed S to go to the VC panel view, instead of getting the VC panel I got a panelless exterior view which spun wildly, non-stop, in the vertical. Pessing S again got me to the normal tower view then back to the unswitchable cockpit rear view....Restoring FSUIPC 3.90 from a backup got FS2002 back to normal.

This has never been reported before, and it did not happen here last time I checked. Furthermore, there is nothing in FSUIPC which touches views and so on unless programmeed to do so. However, I will re-check whwn I get a chance.

I then tried running FS98, which I still have on my system (you don't just dump an classic just because a new version comes out, at least not in this case)! It crashed immediately. After I restored FSUIPC 3.70 from a backup FS98 was back to normal.

Again it worked fine here last time I tested it.

Instead of complaining that the installer is a bad idea and that the website is wrong in its claims, why not try actually reporting your problems as problems, with information, so they can be investigated and sorted?

I will re-check here when I get a chance -- but it may be a couple of weeks time now as I am only back for a few days between holidays.

[LATER]

I just tested the latest, 3.999v, in FS2002 and cannot get anything to go wrong, so without more information on that I can't help much.

It'll take longer with FS2000, FS98, CFS1 and CFS2 because i deleted them earlier this year through lack of disk space. I'll go search for the install disks.and put them on a USB stick.

BTW i don't much mind if you stick with older versions provided you never ask for any support for them. That and new facilities or fixes is all that you'd miss. But the installer will try to keep folks up-to-date -- that's the reason. I assume folks update because they need the new features or fixes or some support.

Pete

[Pete Dowson]

Okay. So far my progress on checking this, with FSUIPC version 3.999v, is as follows:

FS2002:: runs okay. Tried all default aircraft in all view modes, can't make anything go wrong.

FS2000: had a job installing this, and it hanges on loading before I've even installed FSUIPC. I think it might be incompatible with Win7-64 despite selecting compatibility modes.

CFS2: runs okay with FSUIPC 3.999v (see log below, with weather logging enabled).

CFS1: Won't even install on Win7-64.

FS98: i'm afraid I've lost my disks so cannot reinstall this. Must have been thrown out in a clearout a while back. If i'm to debug your problem with this I need details, like logs and Windows error reports givng module offset -- but using 3.999v, not 3.999s.

Regards

Pete

Log from CFS2:

********* FSUIPC, Version 3.999v by Pete Dowson *********
Running on Windows Version 5.1 Build 2600 Service Pack 2
Verifying Certificate for "L:\CFS2\MODULES\FSUIPC.dll" now ...
   SUCCESS! Signature verifies okay!
Running inside CFS2
User Name="Pete Dowson"
User Addr="petedowson@btconnect.com"
FSUIPC Key is provided
WideFS Key is provided
Module base=61000000
LogOptions=00000001
DebugStatus=255
    44797 System time = 07/08/2012 20:23:21
    44875 L:\CFS2\
    52031 System time = 07/08/2012 20:23:28, CFS2 time = 20:23:26 (20:23Z)
    60563 AIRCRAFT\F4U1A_CORSAIR\F4U1A_Corsair.air
    60625 Aircraft=""
    65844 SITUATIO\defgnd.flt
    66109 Clear All Weather requested: external weather discarded
    68688 Advanced Weather Interface Enabled
    68688 Not patched ADVDRV.DLL since offsets don't match!
    68688 SIM1.SIM patched for more accurate altitude holding
   141609  FS98 Pressure=1013.2 mb
   141609  FS98 Wind0: ground (56ft) to 99940ft AGL, dir 0M, vel 0, gust 0, turb 0
   141609  FS98 Vis: range=60sm, (raw value=6000)
   141609  FS98 CurrTemp at PlaneAlt=62: 15C
   144469 WeatherOptions set, now 00000001 (timer=0)
   144469 LogOptions changed, now 00000013 (LogExtras=1)
   144953 ### FS2000 Global Weather Active (allows external control) ###
   144969 >Change:  FS98 Pressure=1013.2 mb
   144969 >Change:  FS98 Vis: range=150sm, (raw value=15000)
   144969 >Change:  FS98 Tstorm: type=0, from 0ft to 0ft (+/- 0ft), cover 0, turb 0, ice 0
   144969 >Change:  FS98 Cloud1: type=0, from 0ft to 0ft (+/- 0ft), cover 0, turb 0, ice 0
   144969 >Change:  FS98 Cloud2: type=0, from 0ft to 0ft (+/- 0ft), cover 0, turb 0, ice 0
   144969 >Change:  FS98 Temp2: to 0ft, Day 0.0C
   144969 >Change:  FS98 Dewpoint Control: disabled
   144969 >Change:  FS98 Precip Control: disabled
   144969 >Change:  Pressure=1013.2 mb (Target is 1013.2)
   144969 >Change:  surface wind: to alt=100000ft AMSL, dir=0T, vel=0.0, gust=0.0, turb=0, shear=0, var=0.0
   144969 >Change:  Visibility[0]: range=60.0sm (96561m), from=-1490ft, to=100000ft
   144969 *VIS* SM: Min=0.00, MaxRny=10.00, MaxOvc=20.00, MaxCld=20.00, MaxClr=60.00, Upper=60.00, FT: LwrAlt=6000, UppAlt=25000
   144969  Results: Visibility[0]: range=60.0sm (96561m), from=-1490ft, to=100000ft
   218625  Results: FS98 CurrTemp at PlaneAlt=518: 14C
   291656  Results: FS98 CurrTemp at PlaneAlt=502: 14C
   337875 Aircraft=""
   340188 SITUATIO\defgnd.flt
   341172 Clear All Weather requested: external weather discarded
   342203 ### FS2000 Global Weather Active (allows external control) ###
   342203 >Change:  surface wind: to alt=1000ft AMSL, dir=0T, vel=0.0, gust=0.0, turb=0, shear=0, var=0.0
   342203 >Change:  Visibility[0]: range=50.0sm (80467m), from=0ft, to=10000ft
   342203  Results: surface wind: to alt=100000ft AMSL, dir=0T, vel=0.0, gust=0.0, turb=0, shear=0, var=0.0
   342203  Results: Visibility[0]: range=50.0sm (80467m), from=-1490ft, to=100000ft
   342203  Results: FS98 Vis: range=50sm, (raw value=5000)
   342203 SIM1.SIM patched for more accurate altitude holding
   347172 >Change:  Visibility[0]: range=50.0sm (80467m), from=-1490ft, to=100000ft
   347172 *VIS* SM: Min=0.00, MaxRny=10.00, MaxOvc=20.00, MaxCld=20.00, MaxClr=60.00, Upper=60.00, FT: LwrAlt=10000, UppAlt=25000
   347172  Results: FS98 CurrTemp at PlaneAlt=62: 0C
   350297 Broadcasting Weather Changed: 00004000
   350516  Results: FS98 CurrTemp at PlaneAlt=62: 15C
   378469 >Change:  Visibility[0]: range=50.0sm (80467m), from=-1490ft, to=10000ft
   378484 >Change:  Visibility[0]: range=50.0sm (80467m), from=-1490ft, to=100000ft
   425766 >Change:  Visibility[0]: range=50.0sm (80467m), from=-1490ft, to=10000ft
   425797 >Change:  Visibility[0]: range=50.0sm (80467m), from=-1490ft, to=100000ft
   435141 System time = 07/08/2012 20:29:51, CFS2 time = 14:30:14 (04:30Z)
   435141 *** FSUIPC log file being closed
Memory managed: 0 Allocs, 0 Freed
********* FSUIPC Log file closed ***********[/CODE]

[scottmiller]

But it does work in both CFS1 and 2. It was only CFS3 where it was not possible. Your previous version must have been many years out of date becayse FSUIPC3 has come with an automatic installer now for about 5 years or so.

Not possible, version 4 is for FSX and later only. It would cause many application programs to fail.

This has never been reported before, and it did not happen here last time I checked. Furthermore, there is nothing in FSUIPC which touches views and so on unless programmeed to do so. However, I will re-check whwn I get a chance.

Again it worked fine here last time I tested it.

Instead of complaining that the installer is a bad idea and that the website is wrong in its claims, why not try actually reporting your problems as problems, with information, so they can be investigated and sorted?

I will re-check here when I get a chance -- but it may be a couple of weeks time now as I am only back for a few days between holidays.

[LATER]

I just tested the latest, 3.999v, in FS2002 and cannot get anything to go wrong, so without more information on that I can't help much.

It'll take longer with FS2000, FS98, CFS1 and CFS2 because i deleted them earlier this year through lack of disk space. I'll go search for the install disks.and put them on a USB stick.

BTW i don't much mind if you stick with older versions provided you never ask for any support for them. That and new facilities or fixes is all that you'd miss. But the installer will try to keep folks up-to-date -- that's the reason. I assume folks update because they need the new features or fixes or some support.

Pete

Pete,

There was no need to get upset about my post. I WAS reporting the problems I encountered with PSUPIC 3.999s as problems and I DID provide information so they could be investigated (in fact, I gave a detailed description of the problems so they COULD be investigated!)! In any case I have every right to state my opinion about the installer, good or bad.

In point of fact, I wasn't being critical of the installer itself so much as the fact that it didn't give the user the option of selecting which versions of FS or CFS to install FSUIPC in (I still think this would be a good idea rather than to assume ALL users would want it installed in ALL versons of FS or CFS. Obviously, this wasn't true in my case.). As I stated in my post version 3.98a came with either QW's Ultimate 757 or PMDG's Queen of the Skies for FS2004. The last version of FSUIPC I personally downloaded prior to version 3.999s was verson 3.90. Where can I get a copy of version 3.999v? The version I downloaded from your web site on schiratti.com only a week ago was 3.999s (I just checked and 3.999s is still the most recent version available). Actually, I'd be just as happy with a full install copy of version 3.98a since I know it works with FS2002 (but not F98).

FSUIPC *might* work in CFS1 and 2 but neither require it to function properly. I checked my last backup of both CFS1 and 2 and not only were neither installed with FSUIPC included, neither has a "module" folder of any kind that would have included a version of FSUIPC. Both, in fact, work just fine without FSUIPC installed.

I hadn't bothered to try to use any version of FSUIPC after 3.70 with FS98 before now (and I wouldn't have tried to install 3.999s in FS98 either if the installer had given me a choice), since all versions after 3.70 come with features that only benefit versions of FS later than FS98 (so far as I can see).

If version 3.999v works with FS2002 then the version 3.999s installer must have screwed up something in the FSUIPC.ini file during the installation process...BTW, just courious, but what are you going to do about the version number for the non-FSX version after you reach "z" (which is only 4 versions away)?

Scott

[Pete Dowson]

There was no need to get upset about my post.

Not upset, rather puzzled is all.

Where can I get a copy of version 3.999v? The version I downloaded from your web site on schiratti.com only a week ago was 3.999s (I just checked and 3.999s is still the most recent version available).

The Schiratti site is not mine and I don't have free access. I post all interim updates to the Download Links subforum here, in this place. I don't do fully revised documentation and Installers for every release -- there have been an average of at least one new release every month for the 14 years I've been doing this. So 3.999s is the last full installer+dox release, interim releases are posted here.

Actually, I'd be just as happy with a full install copy of version 3.98a since I know it works with FS2002 (but not F98).

I cannot make anything go wrong with it in FS2002, as i said. I don't know how to reproduce your symptoms, and have no code in FSUIPC which deals with views or graphics in any case. There's something else going on with your system which I don't know about. As for FS98, I'm afraid i've lost my copy of that. But it works fine in CFS2 for sure, and really anything before FS2002 is treated identically. However, I would be able to check the FS98 problem a bit if I could at least see logs and Windows error reports so I know where it is crashing. This needs to be with 3.999s though so it matches the current code state.

FSUIPC *might* work in CFS1 and 2 but neither require it to function properly.

No version of FS requires FSUIPC to function properly! Folks install it because they want to use it for something! I don't know what you are getting at here.

I checked my last backup of both CFS1 and 2 and not only were neither installed with FSUIPC included, neither has a "module" folder of any kind that would have included a version of FSUIPC. Both, in fact, work just fine without FSUIPC installed.

Only CFS3 had no Modules folder. CFS1 and CFS2 have a similar folder structure to FS98 through FS2004, with most of the FS DLLs in the MODULES folder. I think you are mistaken there. And of course Microsoft were never making products dependent upon my program to function correctly! I don't understand where you get such a notion!?

... since all versions after 3.70 come with features that only benefit versions of FS later than FS98 (so far as I can see).

FS98 was only supported by FSUIPC for two reasons. First as a means of determining how to support FS2000, and second as a supported version of FS6IPC.DLL (which was the original FS98 add-on module) after its author stopped working on that and was recruited into the FS team.

FSUIPC most certainly is NOT needed for any reason I am aware of in FS98. FSUIPC1 came out after FS2000. Everyone needing add-on support in FS98 used FS6IPC.

If version 3.999v works with FS2002 then the version 3.999s installer must have screwed up something in the FSUIPC.ini file during the installation process.

The INI file is not touched at all by the Installer. It can pre-exist or be created as new, but that is done by FSUIPC after loading. And there are no entries in the INI file related to views or graphics.

BTW, just courious, but what are you going to do about the version number for the non-FSX version after you reach "z" (which is only 4 versions away)?

Hopefully, stop FSUIPC3 development before then. It was never supposed to be developed more than 2 years after FSX came out in any case. FSUIPC4 for FSX then FSUIPC5 for FSXI, etc. I don't mind maintaining two versions for a couple of years, but FSUIPC3 has to be frozen. It's just that i'm soft and cave in to folks' requests too easily. ;-). I hope to freeze FSUIPC4 soon s well, excpet possibly for support for Prepar3D Version 2 if that looks possible. If they change to 64-bit I will have to move on to FSUIPC5 for that.

If I do continue after 3.9999z I will start with double letters in the displayed and printed version numbers -- it's just the Application readable version which can't go beyond 'z'.

Pete

[aua668]

BTW, just courious, but what are you going to do about the version number for the non-FSX version after you reach "z" (which is only 4 versions away)?

3.A00a - and by that we have plenty of new versions for FS9 :razz: :razz: :razz:

Rgds

Reinhard

[Pete Dowson]

FS2000: had a job installing this, and it hanges on loading before I've even installed FSUIPC. I think it might be incompatible with Win7-64 despite selecting compatibility modes.

I've managed to get FS2000 running on another PC, with XP-32 bit. I can get into flight mode and it works okay then, but it does crash a while after I enter FSUIPC Options . I'm investigating now. This may not help with FS98 though.

Back later ...

Pete

[Pete Dowson]

I've given up on the FS2000 crash in the options. It's something to do with the video mode. CFS2 which has exactly the same code is fine, it's just the attempt to overlay FS2000's screen with the options dialogue which causes a crash and it is deep down, about 16 nested calls in FS deeper than fSUIPC.

I'm taking your advice. I've changed the Installer to only install for FS9 or FS9.1 (the two variants of FS2004). i'm withdrawing support for FS98, CFS1, CFS2, FS2000 and FS2002. It just isn't possible to support these now.

Version 3.999w includes these changes. I've asked Mr. Schiratti to change the wording on his "Peter Dowson" page accordinlgy.

Thanks for the heads-up on this, and apologies for the inconvenience it caused you.

Regards

Pete

[scottmiller]

I've given up on the FS2000 crash in the options. It's something to do with the video mode. CFS2 which has exactly the same code is fine, it's just the attempt to overlay FS2000's screen with the options dialogue which causes a crash and it is deep down, about 16 nested calls in FS deeper than fSUIPC.

Actually, I haven't had FS2000 installed on my system for quite some time. Uninstalled it after FS2002 came out (the two are too similar and FS2002's graphics were better).

I'm taking your advice. I've changed the Installer to only install for FS9 or FS9.1 (the two variants of FS2004). i'm withdrawing support for FS98, CFS1, CFS2, FS2000 and FS2002. It just isn't possible to support these now.

Thanks, Pete! I'm sorry to see you withdraw support at least for FS2002 though. It was gracious of you to continue to support FS98, CFS1 and CFS2 for as long as you did!

Version 3.999w includes these changes. I've asked Mr. Schiratti to change the wording on his "Peter Dowson" page accordinlgy.

Now that I know that the latest versions of FSUIPC are avaiable here, I'll look for them here instead of Mr. Schiratti's site.

Thanks for the heads-up on this, and apologies for the inconvenience it caused you.

Regards

Pete

No apologies necessary, Pete. I was mystified (never having had any problems with upgrading FSUIPC before. My first version was 2.74, or there abouts) more than anything else!

Scott

[scottmiller]

Not upset, rather puzzled is all.

The Schiratti site is not mine and I don't have free access. I post all interim updates to the Download Links subforum here, in this place. I don't do fully revised documentation and Installers for every release -- there have been an average of at least one new release every month for the 14 years I've been doing this. So 3.999s is the last full installer+dox release, interim releases are posted here.

I cannot make anything go wrong with it in FS2002, as i said. I don't know how to reproduce your symptoms, and have no code in FSUIPC which deals with views or graphics in any case. There's something else going on with your system which I don't know about. As for FS98, I'm afraid i've lost my copy of that. But it works fine in CFS2 for sure, and really anything before FS2002 is treated identically. However, I would be able to check the FS98 problem a bit if I could at least see logs and Windows error reports so I know where it is crashing. This needs to be with 3.999s though so it matches the current code state.

No version of FS requires FSUIPC to function properly! Folks install it because they want to use it for something! I don't know what you are getting at here.

Sorry, Pete, I was simply trying to say that CFS1 and CFS2 are installed they no module folder is created and no FSUIPC installed in it (at least this is the case when I install CFS1 and CFS2 on my system.

Only CFS3 had no Modules folder. CFS1 and CFS2 have a similar folder structure to FS98 through FS2004, with most of the FS DLLs in the MODULES folder. I think you are mistaken there. And of course Microsoft were never making products dependent upon my program to function correctly! I don't understand where you get such a notion!?

Well, CFS1 and CFS2 may have a similar folder structure to FS98 through FS2004, but like I said above. CFS1 and CFS2 lack a module folder. Like I said, when I checked my most recent backup of CFS1 and CFS2 no module folder was found in either one. Thus, they don't need FSUIPC installed to run properly. Since Microsoft didn't include a module folder in either CFS1 or CFS2 it must not have anticipated anyone wanting to use FSUIPC with either one.

FS98 was only supported by FSUIPC for two reasons. First as a means of determining how to support FS2000, and second as a supported version of FS6IPC.DLL (which was the original FS98 add-on module) after its author stopped working on that and was recruited into the FS team.

FSUIPC most certainly is NOT needed for any reason I am aware of in FS98. FSUIPC1 came out after FS2000. Everyone needing add-on support in FS98 used FS6IPC.

If I recall correctly an FS98 addon (I don't remember which one) required a non-registered version of FSUIPC to function correctly.

The INI file is not touched at all by the Installer. It can pre-exist or be created as new, but that is done by FSUIPC after loading. And there are no entries in the INI file related to views or graphics.

Well, all I know is that FSUIPC version 3.90/3.98a work fine with FS2002 and version 3.999s does not. Therefore the only reasonable explanation possible is that the problem is with FSUIPC 3.999s or something it does with my installation of FS2002, not with either my system or FS2002.

Hopefully, stop FSUIPC3 development before then. It was never supposed to be developed more than 2 years after FSX came out in any case. FSUIPC4 for FSX then FSUIPC5 for FSXI, etc. I don't mind maintaining two versions for a couple of years, but FSUIPC3 has to be frozen. It's just that i'm soft and cave in to folks' requests too easily. ;-). I hope to freeze FSUIPC4 soon s well, excpet possibly for support for Prepar3D Version 2 if that looks possible. If they change to 64-bit I will have to move on to FSUIPC5 for that.

Freezing development of FSUIPC is probably a good idea. I don't imagine many, if any, new addons for FS2004 might need anything the current version of FSUIPC doesn't already have.

If I do continue after 3.9999z I will start with double letters in the displayed and printed version numbers -- it's just the Application readable version which can't go beyond 'z'.

I like Reinhard's suggestion...another idea would be to incorporate "FS9" and"FSX" into the name (i.e., FSUIPCX_FS9.exe)

Pete

[Pete Dowson]

Well, CFS1 and CFS2 may have a similar folder structure to FS98 through FS2004, but like I said above. CFS1 and CFS2 lack a module folder. Like I said, when I checked my most recent backup of CFS1 and CFS2 no module folder was found in either one. Thus, they don't need FSUIPC installed to run properly. Since Microsoft didn't include a module folder in either CFS1 or CFS2 it must not have anticipated anyone wanting to use FSUIPC with either one.

I don't understand how your CFS1 and CFS2 can possibly work without the Modules folder. I have re-checked this by reinstalling them, and both clearly, by default, not only have a Modules folder but one with most of what constitues the simulator's code in it (the usual DLLs).

No version of FS or CFS ever needs FSUIPC to run properly, but most certainly all before FSX excepting CFS3, certainly need the Modules folder. (Note "Modules", not "Module")

FSUIPC1 and FSUIPC2 were made to support CFS1 and 2 because users requested they do, and it performed the same function for them as it does for the mainstream FS versions. It is nothing to do with them "needing" FSUIPC to operate "properly". I've no idea what you mean by that.

If I recall correctly an FS98 addon (I don't remember which one) required a non-registered version of FSUIPC to function correctly.

No, it would have been Adam Szofran's FS6IPC. For FSW95, the first Windows version of FS it would have been his FS5IPC. The only use of FSUIPC on FS98 was for Logging, and I made that work on FS98 purely so I could ensure compatibility of the Offsets for FS98 applications used with FS2000.

Freezing development of FSUIPC is probably a good idea. I don't imagine many, if any, new addons for FS2004 might need anything the current version of FSUIPC doesn't already have.

But you are misunderstanding the most major use of FSUIPC as it is and has been for many years -- not as an aspplication interface, which has hardly changed at all for many years, but as a more flexible way of interfacing hardware controls and external indicators, and, via the Lua plug-in facilities, of extending the FS capabilities and subsystems. The actual application interface, via the offset provision, for which it was originally designed, has barely changed in many years at all. The only reason FSUIPC3 has reached 3.999s has been for all the other aspects now supported which I assume you are not actually aware of and perhaps don't even use.

I like Reinhard's suggestion...another idea would be to incorporate "FS9" and"FSX" into the name (i.e., FSUIPCX_FS9.exe)

The naming is not relevant. The only restriction on the version numbering is in its application-readable counterpart, via a 4 byte offset. The convention there only allows 3.nnnX where nnn are decimal and X is alpha.

Pete

[scottmiller]

I don't understand how your CFS1 and CFS2 can possibly work without the Modules folder. I have re-checked this by reinstalling them, and both clearly, by default, not only have a Modules folder but one with most of what constitues the simulator's code in it (the usual DLLs).

No version of FS or CFS ever needs FSUIPC to run properly, but most certainly all before FSX excepting CFS3, certainly need the Modules folder. (Note "Modules", not "Module")

FSUIPC1 and FSUIPC2 were made to support CFS1 and 2 because users requested they do, and it performed the same function for them as it does for the mainstream FS versions. It is nothing to do with them "needing" FSUIPC to operate "properly". I've no idea what you mean by that.

No, it would have been Adam Szofran's FS6IPC. For FSW95, the first Windows version of FS it would have been his FS5IPC. The only use of FSUIPC on FS98 was for Logging, and I made that work on FS98 purely so I could ensure compatibility of the Offsets for FS98 applications used with FS2000.

But you are misunderstanding the most major use of FSUIPC as it is and has been for many years -- not as an aspplication interface, which has hardly changed at all for many years, but as a more flexible way of interfacing hardware controls and external indicators, and, via the Lua plug-in facilities, of extending the FS capabilities and subsystems. The actual application interface, via the offset provision, for which it was originally designed, has barely changed in many years at all. The only reason FSUIPC3 has reached 3.999s has been for all the other aspects now supported which I assume you are not actually aware of and perhaps don't even use.

The naming is not relevant. The only restriction on the version numbering is in its application-readable counterpart, via a 4 byte offset. The convention there only allows 3.nnnX where nnn are decimal and X is alpha.

Pete

Ok, time to pull my foot out of my mouth, Pete. I took a second look at both CFS1 and CFS2 and discovered that both indeed DO have moducle folders! I have no idea where I got the mistaken idea that they didn't! Sorry about the confusion all this caused! Must have been due to a lack of sleep (I've been watching the London Olympics almost non-stop since they started)....

Scott