Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. How would you use it? Are there now programs which receive NMEA 0183 signals on USB? I've got the offical NMEA specifications and they only lay down standards for RS232 and similar serial links. They may be out of date now, of course, so do you have revised details? The other problem which I don't really know how to deal with is a USB device driver. All USB thngs seem to have to either abide by certain global standards (HID, such a joysticks, keyboards, mice, and Disks or similar storage devices for instance), or need specifically-written drivers. So where would these come from? Do the makers of the software you've got which can read NMEA on USB supply drivers for writing it too? If you are looking to use USB simply because you have no serial ports available, then there are serial port adapters for USB which do the job. I think they are quite cheap too, now. Regards, Pete
  2. Don't they already? I wasn't aware there was any change in the format. In fact I'm sure I've loaded them on FS2004 already. Can you elucidate please? Regards, Pete
  3. Not a menu, I think there's far too many of those already. how about a HotKey, you could define it in the INI file? A toggle. All "aircraft settings" should be saved in the Flight file. that's what it's for. AutoSave doesn't save any files at all itself, it simply calls the same routine as FS's Flights-Save menu option. What's missing? Look in a FLT file and see all the stuff FS saves. I can only think these are 3rd party add-ons doing their own thing and not using FS values. There's really no way I'd have acces to those even if AutoSave was to get involved in file transfers. This is really something the aircraft/panel makers could take care of themselves, like the .FMS files saved by one well-known example. Really? That's an FS deficiency then, and should be reported to Micrsoft! Again, I'm not sure I can even get the data let alone restore it on reload. All that stuff is done by FS, not I. Sorry. Regards, Pete
  4. Thanks for letting me know. Glad you sorted it! Pete
  5. I don't know VB, but normally the result is merely an indication of success or failure. The FSUIPC_Read operation reads a block of memory, it isn't specifically an integer or anything else. It could be a whole batch of integers, or a string of characters, et cetera et cetera. What you then treat the data as will vary according to what you are reading and how you want to use it. In C/C++ "long" is the same as "int". Do you mean unsigned as opposed to signed? If VB cannot handle unsigned numbers then, I'm sorry, I don't know what to advise you. I've no idea how you get 255's for full flaps -- the Integer value is 16383, or hex 3FFF. If you only read one byte (character) you'll get 255 (the FF in the first byte), but that could equally refer to 63 other flap positions (00FF to 3EFF, hex 3F = 63 decimal). The pitch and bank values are easy, because they are simple signed 32-bit integers, which I'm sure is the default Integer value type in VB. But it is 4 bytes you need to tell the Read routine -- if you are getting 255 for full flaps it sounds very much like you are reading only 1 byte (8-bits) and so only getting a quaerter of the total data needed for a 32-bit integer. Regards, Pete
  6. Just delete WideServer.DLL. FSUIPC doesn't know or care about it -- it's the other way round, WideServer needs FSUIPC. Regards, Pete
  7. If you have the original email from SimMarket, just print it and save it, keep it safe as you would anything else you pay for. if you want to use the programs on a different PC just enter all the details again, exactly as before. Same if you need to re-format your disk or re-install Windows. If you've already lost the email notification but still have a registered installation, then make a safe copy of the FSUIPC.KEY file (it's in the FS modules folder, with FSUIPC), or even print it out for future reference. it is an ordinary text file and can be read and printed. If you've already lost the keys and overwritten the FSUIPC.KEY file, then you will have to explain the situation to customer services at http://www.simmarket.com. Provide the same name and details as you did originally and they should be able to find you on their database. Regards, Pete
  8. AhI believe there was a problem originally with FSNav. I think you may need to go download the latest version. The first version issued for FS2004 did cause problems. Sorry, i did not remember that myself either. Regards, Pete
  9. Please let me know. First make sure the DLL is okay by re-downloading it. Also, if there is an FSUIPC.LOG file produced, let me see it. Also try adding "InitDelay=10" to the [General] section of the FSUIPC.INI file (this will be in the Modules folder -- if there isn't one, just make a small Text file in Notepad containing just [General] InitDelay=10 and save it as "FSUIPC.INI" in the Modules folder.) Let me know, whatever, please. Regards, Pete
  10. All I can think of is reading the real axis using the appropriate EPL command and then set it to the POV or Soft Axis. f you do this in a loop with a delay it should work, I think. (My memory of EPIC matters is disappearing fast I'm afraid :? ). Regards, Pete
  11. Sorry, no I haven't. Are there no messages? What actually happens? Is the an FSUIPC.LOG or FSUIPC.INI file created in the Modules folder? Which version of FSUIPC did you install? Do you have any other add-ons in your FS2004 installation? In case your copy of FSUIPC.DLL is corrupted you should re-download it and check again. Really, until you register it or run some program which interfaces to it, it is doing nothing much at all. If you have something installed which uses it then maybe that is causing the problem. Try deleting the FS9.CFG file to make FS generate a new one (you'll have to reset all the FS options if you do this). Also temporarily remove any other third-party DLLs installed in the Modules folder, if you have add-ons installed. Regards, Pete
  12. I think the granularity is 100 fpm, and I don't see any way to change it. Sorry. Regards, Pete
  13. No sorry. It does really sound like a sound problem (sorry, no pun intended). Try using DXDiag and reducing the DirectX sound acceleration one notch, then two. I have heard this gives smoother frame rates in FS too as it spends less time filling up the sound cards buffers. Regards, Pete
  14. No. I think that is defined in the AIR file. It may be overridable in the AIRCRAFT.CFG file. Creep up to 5000 feet? Use the afterburners for take off and point the nose to the sky on rotation! It will reach 5000 feet before you know it! :D 100 fpm is the default? Surely not? Even a Cessna defaults to several hundred feet per minute. I know nothing which defaults to 100 feet per minute -- that's only a little over 18" per second! I can go up stairs faster than that and I'm 60 years old with no jets attached! :) Anyway, the V/S you need will be completely different at different altitudes. You should not leave it (cannot leave it!) to any "default", you have to set it using the V/S setting for the A/P. Regards, Pete
  15. Actually I could get round both those problems simply by watching for changes in the FS standby frequencies and copying changes to the PFC display. The only part I wouldn't want to do is the reverse -- have the PFC controls manipulate the FS standby and swap operation. As you may have noticed, on the PFC avionics it is much more efficient and responsive to adjust the standby then swap, rather than adjust the main frequency directly -- try the latter on one of the NAV's when the standby display shows the radial to see what I mean. The reason for this difference is that the standby frequencies are currently totally contained within the PFC driver, but for changing in-use frequencies each increment and decrement has to be passed on to FS. Provided you don't display or use the FS radio stack on screen, if PFC copies change FS standby values to the PFC avionics, that would meet the need, wouldn't it? If so I'll add it to the list. Regards, Pete
  16. [quote name="Frank.O What about this one' date=' Pete?
  17. No bug that I've heard of. The only one so far was a problem in versions 3.00 and 3.01 of FSUIPC with names containing accented characters (all fixed long ago). And, so far at least, there's only been one mistake I know from SimMarket, and that was issuing two FSUIPC keys to someone instead of one FSUIPC and one WideFS. Maybe they got your request mixed up, but it would be most unusual. The emailed details themselves are generated by program so should be free from error (famous last words :D ), or at least self-consistent. In ALL the other instances of user problems it has been incorrect data entry. Your name, email and Key must all be exact to the character. Computers are stupid, they believe what you tell them. Try cutting and pasting from the SimMarket email if you are not sure. There's no change in keys for different versions and will not be till at least version 4, which won't happen till FS2006, earliest. :) --- unless something drastic happens which forces me to change the system, of course. :shock: Good. glad it is sorted. BTW it is "SimMarket" not "SimWare", just in case this confuses other readers. SimWare are a well known flight-Sim add-on dealer operating out of Belgium (I think), and is quite distinct from SimFlight and SimMarket. Regards, Pete
  18. Not a problem. That's what this forum is for. Regards, Pete
  19. Yes. It will be a Beta version with a time limit anyway. Probably end November now. Just keep the numbers reasonably low please. Write to me at petedowson@btconnect.com and I'll send it by reply there. I'll have it ready over the weekend some time. Regards, Pete
  20. If you are talking about FSUIPC version 3, yes. You can actually check these things by looking at the FSUIPC LOG. There's no free developer's key. I'd really hoped that developers would actually register FSUIPC, as I don't charge for either developer support nor all the work on the SDK. If you really don't want to register then you'll need an access key for your program. The access registration documentation in the FSUIPC SDK will tell you all about that. Correct. But if you want your program to be used by other, non-registered, folks then it will need the key. Yes. If it is free ware (or you make a small charge merely to cover distribution costs, for instance) then the key would be free. If you want an interim key (one with a time limit on) whilst you are developing and before you've decided about free/payware status, let me know. You'll need to send an email to my standard email address -- see the details in the Freeware Keys "sticky" above. But please read the registration document first. The two methods are alternatives. The manual entry facility was only to allow older programs or modules or gauges to be registered without making program changes. It is better for the user if the registration is done automatically by the program. Regards, Pete
  21. Once I've done them, they're in, unless I'm suspecting problems, which in this case I'm not. However, I've no schedule for 3.12 at present. Would you like an interim Beta version to test with? Regards, Pete
  22. WideFS is no longer freeware, and you cannot use Version 5 WideFS or earlier with FSUIPC 3 or later. You need WideFS 6 and it is not free. Sorry. Regards, Pete
  23. Ah, yes. Enrico is a whole generation and a half younger than I! :) Yes. Regards, Pete
  24. With only WideClient on the client PC, you've got nothing to run on WideFS. You've got everything on the Server! There's no point in running WideFS in that case. You could install all the following programs on the Client instead, and save the Server taking a lot of processor and memory from FS: ActiveSky wxRE, Squawkbox, ServInfo, Roger Wilco and maybe also RWTS, but I don't know what that is. If you moved all this it would be a good idea to have your Internet connection for ActiveSky, SB and RW on the client too, not via the Server which will put more load on the Network needlessly. Yes, well obviously then you need to install SB and Servinfo on the Client. You install programs on the machines on which you want them to run. This is normal practice with computers. :D This is presumably because you told WideClient to load and run Servinfo on the Client from the client's C: disk, and you forgot to install it there? There's no way WideClient can run a program which isn't available. Windows error 2 is "file not found". Regards, Pete
  25. Ah, wellI can't keep doing this stuff forever. There'll be other and better alternatives one day, surely? Maybe I need a young apprentice to train up? :lol: Thank you very much! You've made my day :D :D Regards, Pete
×
×
  • 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.