Dave March

Wow! The repeating flaps one, flaps one, flaps one is not something you mentioned before... at least not that I remember ;-) Anyway this is obviously not an issue for Pete and I would suggest you either move back to the FDC support forum or email me, as I do not visit this forum on a regular basis.

Pete Well I don't think it's quite as easy as that and I would have to provide an interim version of FDC for the user to run so I could see exactly what is occurring. In the case of the 737 FDC does expect to work with values in 0BDC of 0, 2048, 4096, etc. (and yes we do round our calc's). During normal flight operations we also wait for the movement between détentes to complete before making our audio callouts to confirm a flap setting. Eg. we monitor 0BDC until it matches one of our expected values. However, what I think is happening here is the hardware lever is probably positioned somewhere between two détentes when we make our initial checks (when the program starts) using offset 3BFA and 0DBC to determine the current position or the flaps. Sorry, I don't agree. As mentioned above we do check for movement between détentes but if a value in 0BDC falls way short of what it should be when movement stops then that would not be permissible. It's always strange, as you know only too well Pete, when something that's been working without any reported problems for many years suddenly rears its ugly head to bite you where it hurts. Thanks for your input

Wow! Really? Just for the record FDC is not crashing.... it detects a problem, writes to an error log, displays a message to the user, disconnects from FS then ends! If I run this B737.EXE program alongside FS and FDC, using keyboard commands to select flaps, everything is fine and runs without any problems, but of course I do not have any hardware attached and I believe the issue only occurs when the user moves his hardware levers. My 'guess' is the data at x3BFA and/or x0BDC is not what I'm expecting. Probably caused by varying lever movements rather than moving from one détente to another.

Pete, I believe this user was attempting to use an early version of FDC which does not work with FSX, consequently he would have been using FSUIPC3.x too.

Certainly not one of my messages either! :?

Are you sure it's version 3.0... check the main menu screen. I believe someone else had a similar problem this week from the same source and they had version 2.0 !!! If this is the case please visit http://www.aerosoft.com and download the free version 3.0 upgrade

Best wishes to you too Pete. I hope you'll be giving your fingers a little rest for a few days or do you suffer from withdrawal symptoms? :wink:

Early versions of FDC version 3.0 certainly did have an older version of FSUIPC in the installer but Aerosoft corrected that and the current download and CD versions... for many months now... certainly do (to the best of my knowledge) have a more recent one. However, there are always new versions of FSUIPC being released by Peter so it's always best to ensure you have the most recent version anyway.

Just for the record there are no requirements to start FDC before or after Radar Contact. That issue was addressed way back in version 1.2, released 30th January 2003. Taken from that readme and subsequent readme's under the heading 'Version History' MADE a small change to ensure compatibility with Radar Contact 3 where we were getting some Hotkey contention. This change should allow you to start RC3 and FDC in any order rather than having to always start RC3 first.

Well before you start jumping up and down perhaps you ought to think about this a little more. Let's say Pete now decides to call-it-a-day and shelve FSUIPC. What happens to all those addons you currently use when you upgrade o FS2004? I can tell you, they won't work!! Not even if you installed this new module!! My own programs would need a considerable amount of re-coding to use this new module and if I had to spend that much developement time on them I would be selling them as completely new versions too... no free upgrades.... and I'd guess the majority of developers would have to do the same. As a user I'd much prefer to purchase FSUIPC and as a developer I most definately do not want to see FSUIPC discontinued!! Of course there's a place for this new module and it will probably suit the freeware developers more so than others, although currently it doesn't offer anywhere near the same amount of features as FSUIPC. Obviously that may change in the future.

I've been watching (with interest) the various posts regarding the above subject matter and thought it about time I inserted my 2 pence worth. As a freeware and commercial developer of FS software I whole heartedly support Pete's decision to charge for his work and I doubt any FS commercial developer would feel any different. The very same day I heard of the FSUIPC donation scheme my company coughed up and we have since discussed our future needs and arrangements with Pete for continued use of FSUIPC. Without this brilliant module I would guess 90% of the current FS addons we all love would not function at all. As far as us developers are concerned Pete Dowson does a superb job and certainly never ceases to amaze me. He's always been more than helpful in providing those little extras during my projects. As a user I will also gladly pay for full usage of FSUIPC functionalty, as I personally find it something I would not like to be without! Pete: I'd suggest locking down these ever growing threads (and concentrate on FSUIPC/FS2004 :lol: ) because those complaining will eventually discover they have nothing to complain about! Regards