Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. The fiddle factors are just that -- non-dimensioned multipliers adjusted interactively by me to get the best results. I tried them with most, but not all, of the default FS aircraft, and got good results except for speed control where the oscillations were still present when I released it. I'm sorry, but optimising is really a trial-and-error process. If you do find better values please let me know, but the current ones are certainly good with both the Cessnas and Boeings. I could imagine there'd be problems with aerobatic aircraft with fast roll rates, but it surprises me that a King Air doesn't stabilise quickly. Regards, Pete
  2. But you imply that all was well until you re-installed FS9. So something has changed there. FSUIPC doesn't actually do anything which involved lots of computation of delays. It doesn't deal with any graphics, or files. A regular 2 second stutter sounds suspiciopusly like something else running in the background, unless one of the gauges or other add-in modules has something on a 2 second cycle. FSUIPC operates on a frame rate related cycle. There isn't anything on a longer cycle than half a second (this latter is for computation of some values not needed on every frame). Have you checked the FSUIPC log? Is your FSUIPC user registered? If not, this may be down to an access check failing from one of their modules and being retried every 2 seconds. Unlike PSS to fob folks off so. They certainly haven't contacted me, and they've always done so in the past when they've had any problems. I suspect they are desperately trying to resolve this and just want folks to leave them be till they solve it. Regards Pete
  3. If you have distance and bearing (d, b) then you can convert that to some x, y coordinates for a Radar screen. It's simple trig isn't it? Tell me where you are stuck. To keep things easy I tend to do this sort of trig in the four quadrants separately -- saves confusion with signs and so on. For the first quadrant (bearing 0-90, Forward/Right), the (x,y) plot position would be: x = d * cos(b) y = d * sin(b) after converting b to radians of course ( *PI / 180). The other quadrants are variations of this with different sinces and +/-90 sort of fixes. On the other hand, just to map positions relative to the aircraft you don't need distance and bearing. Just use the Lat/Long values, made relative to the user aircraft by subtracting the latter. However, then you'd need to rotate the relative (x,y) coordinates to get bearing up, so you might be better off using distance and bearing in any case. But TrafficLook merely lists the data, including distance and bearing. it doesn't draw a map. You already have the data that TrafficLook has. Regards, Pete
  4. Other than by a process of elimination (i.e. remove each possible candidate in turn), no, I'm sorry. The FS control system operates by Posting Messages and there's no way of tracing them back. Regards, Pete
  5. WideFS cannot run parts of FS on other PCs, it only runs other programs. The PMDG aircraft are made up of parts of FS -- DLL files, MDL files, CFG files, Textures, Sounds and Gauges -- all of which need FS in which to run. They are not separate programs and cannot run alone. Regards, Pete
  6. Where's the Log? Pete
  7. There's no definition of Modular interfaces provided by Microsoft, except those for PANELS.DLL for those writing gauges, and a few more recently for extraction AI information. For all other purposes it is a matter of decompiling, disassembly, and tracing. i.e. hacking into the FS code to work out what does what. I would suggest you wait for FS2006 now, though. Regards, Pete
  8. It returns whatever FS gives to FSUIPC when it asks for ATC type. I think, if the ATC_TYPE entry is missing in the Aircraft.CFG file it may give me the UI manufacturer instead. This is why I mention that it is "generally the make" in my documentation. Use "TCASId=Model". Regards, Pete
  9. No. I'm sorry, but I'm afraid FSUIPC doesn't interfere with any of those assignments unless you sepcifically re-program them, and it certainly has no way whatsoever of getting between FS and its Jeppesen weather downloads. For some strange reason everyone always assumes FSUIPC is to blame for anything odd, but it is very rarely the case. Pete
  10. It's being used okay. Even the speed control (which isn't so well behaved) is now being used successfully for taxiing. Let me know what you are doing and I'll try to spot where you are going wrong. Regards, Pete
  11. What is the AutoSave.CFG file set to do? i.e. how often is it saving files? Is it 17 seconds or so? Sounds rather frequent. Are you running an aircraft which saves its own files too, whenever AutoSave does? For instance, the PSS Concorde does this. I've no other way of accounting for two pauses with 2 seconds between. If saving Flights causes a noticeable stutter then one or more of the following are true: 1. The hard disk partition containing your "My Documents" folder is getting full. 2. The disk is very fragmented. 3. Windows write caching is disabled. 4. You are rather short on real memory. Regards, Pete
  12. Show me the Log file and INI files for the Client and Server. Pete
  13. Problems in 3.30 are fixed in 3.47. Pete
  14. 1. Please find the "Caps Lock" button on your keyboard and press it so that you can get lower case letters too. All capitals makes it more difficult to read, and it comes across as shouting. 2. The symptom is usually caused by a bad User key. Please ZIP up the FSUIPC.KEY file (in the FS Modules folder) and send it to me at petedowson@btconnect.com. Regards, Pete
  15. The problem appears to be that the Product and Company names have been changed. The Freeware keys list above lists these as: But from your log the names now two spaces and one space in front of them now, so they won't match. Regards, Pete
  16. Sorry, I really don't know. I don't have or use Squawkbox so I don't know how it's PTT is driven at all. Don't they have a support site? Regards, Pete
  17. I'm back but I'm afraid I am not much help here. There's nothing WideFS ever loops and waits for, and it never changes the mouse pointer. It sounds very much like a Network driver or configuration problem. Rather than re-installing the complete operating system, try just uninstalling and re-installing the etwork hardware and software. Regards, Pete
  18. No, it should send three KEYDOWN and KEYUP pairs. This could be checked using Microsoft Spy++. Regards, Pete
  19. Not with FSUIPC, no. Regards, Pete
  20. You either need to tell WideClient where you want to send the keypress (this is easy if you use the Run.... options to load that program, see the Documentation), OR set "UseSendInput=Yes" in the INI file. Please check the WideFS documentation. There are a lot of ways to do this. Which one is best depends on the program concerned, and I simply do not know them all. Regards, Pete
  21. That's been around for a long time. No. It isn't really possible as far as I can see. The wind smoothing in FS2004 is completely separate and independent of the weather source. It acts at the aircraft only, it doesn't change the winds so much as change the effect on the aircraft. Regards, Pete
  22. Just updating FSUIPC doesn't change any of that. Without knowing what you've done with trim I'm agraid I can't comment. The other matter sounds like a driver problem. If i were you I'd go back to drivers that worked. Regards, Pete
  23. Sorry, I don't know VB.NET. Isn't the example for VB any use with VB.NET or is the .NET version a completely different language? :cry: Pete
  24. That is the exact symptom I would expect if there were an illegal user key for FSUIPC or WideFS in the KEY file. Some folks have been using an illegal key generator program to make keys and avoid paying. If you'd like to zip up your KEY file and send it to me at petedowson@btconnect.com I will check it out. Give me your details too and I'll see if you've been deceived somehow. Regards, Pete
  25. 1) PFC.DLL assigns the ALt Air switch to the "Carb Heat/Anti-Ice" control by default, on bith Jeys and Props. 2) The "Carb Heat/Anti-Ice" control is in PFC.DLL's drop down losts of controls which can be programmed in any case. You do not need FSUIPC for controls suported already in PFC.DLL. I'm not sure what resolution is possible for something that's never been changed and which works fine. Perhaps you could explain in more detail if you don't get the correct control programmed by default? Why should it be? Normally regular stuttering like that is due to another process running automatically in your PC, like virus checking, memory optimising, TCP/IP address resolving, etc. Check all your background processes, kill those you don't need. 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.