scruffyduck

mine has certainly worked with each time I have updated the dll. AS far as I know Pete have never 'broken' the way the ini file operates as FSUIPC goes to a new version. Just make sure to only copy the new FSUIPC.dll into the modules folder and nothing else

I think all that is in the FSUIPC.ini file which will not be affected if you just copy the latest FSUIPC.dll into the modules folder. If you want to be doulbe sure then rename your current FSUIPC.dll to FSUIPC.old and then add the new one. After you are satisfied it works delete the old one. To be triple sure set a restore point first (assuming you are using XP :D )

Joe If the version of FS2004 you have is 9.01.40901 then this is the latest version. It seems like you do not have the latest version of FSUIPC loaded. You should have version 3.47. If not then you can download it from here http://www.schiratti.com/dowson.html This is not a problem with FS2004 but with FSUIPC. If you have created a new install then did you install FSUIPC yourself or have you also installed some add-on products. If you have not then go to your flight FS9 folder something like c:\program files\microsoft games\Flight Simulator 9 and open the folder called 'modules' In there you will find a file called FSUIPC.dll. It should be dated 4th March 2005. If you right click on that file and select properties then the version tab you can check which version you have. If it is 3.47 then this is a different problem. Other wise temporarily rename it to FSUIPC.old and then run FS again - it should now start. If you do have addons that installed FSUIPC then just get the new one from the site above and follow the instructions to put the updated file into your modules folder Again this is almost certainly not to do with the FS program you have hope that helps

Ah not very useful then :? :?

Have you looked at the FS controls list? I seems to recall that those can be used to change control surfaces as they take a parameter. Some allow incremental change mimicing the keyboard. The list is in the FSUIPC SDK - they are all driven through one offset

How often are you writing the data back - if you want to control the aircraft position etc is the sim in normal mode or slew mode? I would expect things to be slower if you have your application on a separate machine - try it on the FS machine and see if it makes any difference

no problem - if he needs any more help have him pm or mail me

Pete is away until April 2nd. As far as I know FSUIPC reads the aircraft name thru a specific offset (my program does it) since this is just a set of up to 255 bytes there is no obvious reason why FSUIPC should not pass what it sees - a sequence of bytes. Provided that the ASCII code for ' is less than 255 then it should pass through. If memory serves me it is decimal 39 so it should be fine. Which programming language are you using and are you using the standard SDK code for FS interfacing? I must admit that I cannot remember reading a plane name in which had a ' in it - but I will try it next time I have my development environment open. With VB.Net I read the data as an array of bytes and then convert them in a loop to a string using the Chr() function to change the byte into a character

Pete is on vacation until April 2nd or 3rd. My guess is you will have to wait until he returns

As I seem to recall this offset is indeed read only so an attempt to write to it will result in FSUIPC reporting an error. Does it have any material effect on the user then?

control 66297 is the autofeather toggle - presumably that will also affect the annunciator light - or are you trying to change the light without the autofeather being set? Each time you write to it the current status will be reversed If you can't find the offset in the programmers SDK then you can use FSInterrogate to see which offsets (if any) change when a control or insturment is changed in FS - it is the three step process

The SDK from Pete's webpage includes the basic code to read and write using VB.Net. Are you looking for something else?

You might want to check in the FS2004 Control List which comes with the SDK - I am pretty sure that most of the light switches are listed in there

I use Airplan and it requires that you register FSUIPC in your own right. I have a registered version and the Airplan moving map works fine. It's payware so Dean would have to negotiate with Pete for a key if he wants to provide access to FS 'free of charge'. Since AirPlan is essentially a real world flight planner (that's what I use it for) I would expect FS access to be lower on Dean's priorities

Oh b*gg*r :oops: :oops: that will teach me to make sure I am using the latest SDK - Sorry Pete case of not RTFM :D :D

Hi All I am facing up to the fact that I will need to re-write my application in VB.Net. My currrent development environment is not going to hack it long term and now might as well be the time :? I have run the VB code from the SDK thru the VB6 converter which, as I expected, has thrown a bunch of errors. Is there some kind soul out there who has moved the FSUIPC interface module to VB.Net and would be prepared to let me have the conversion? Save me from re-inventing the wheeL Many thanks in advance :D :D

Sorry Pete bit off topic but I wondered if you had any insight into the meaning of the different keywords as a result of your autosave module? Most of them are self evident but some are not - seems that this is where payload data is saved in the payload section and the list is given by payload station which is quite handy. I am pretty sure I can generate a flight file from my program but I would like to understand the keys and values as well. Does not seem to be in the SDK thanks

I'll take a look :D

OK thanks Pete there is no point in using the offsets if they do not actually affect the flight model since that is the whole point of changing the payload. I know that AC Loader actually changes the aircraft.cfg file. Do you by any chance know if this is only read when the plane is loaded or read during the flight? cheers

OK Pete Thanks for clearing that up I will focus on the payload offsets ======================== Just been looking at the old thread from Jose plus FSInterrogate. looks like the payload stations are now marked read only as well. I will play aruond with them a bit and see what happens

Hi I am trying to change the weight of the aircraft using offset 3BFC without much success. I would like to find a reasonably easy way to modify the payload of the aircraft but although FSInterrogate indicates that it is possible to write to this offset it does not seem to stick in FS9. I can't change it using FSInterrogate although I can change it very temporarily by writing directly to the offset but FS changes it back again to the value that it has almost instantly. Also if I change the values for payload in FS and use the 3-scan method offset 3BFC does not come up although the read only ones do. I cannot find any other writable offset except the ones at offset 1400, but I was hoping for a more simple way to modify payload so any help would be much appreciated

Yes you can do it using FSUIPC but you will need programming skills if you want to sue the information in an external program. You will also need the FSUIPC programmers SDK which is on Pete's web page http://www.schiratti.com/dowson.html You should ask questions about FSUIPC in the Peter Dowson Support Forum which is lower down the forum list on simFlight

You need to post this in Peter Dowson's support Forum - it is lower down in the forum list

Hi Pete Just released my first alpha version to a couple of testers. Wanted to say thanks both for a great product in FSUIPC and for your patience in answering my many questions :D

Thanks Pete - apologies for my obtuseness :D I was hoping for an easy answer but I will do some experimenting. I'll document what I get