Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by airforce2

  1. I had something similar going on, and finally tracked it to a change that had occurred in my FSUIPC.ini that had removed the line: RemoveATC=Yes This caused the old ugly atc.dll CTD to come back and haunt me for the majority of one very frustrating weekend. No idea how the ini file was changed, but I went back to my saved copies and it looks like the change happened around the time I upgraded to 3.70 There had been a few random dumps...but a few weekends ago I found a flight profile that really tickled the atc.dll bug and it was a steady stream of midflight CTDs. Once the param was put back...voila. Regards
  2. You might try changing var names...you are using same vars as defined in the functions (i.e. "Param"). The scopes look OK at first inspection, but could be a var is being mis-cast...in particular, Param cast as type Byte could have this effect. Also, given that these are defined as functions, calling them as subroutines looks strange to me... Agree with Pete that you'll need to engage in some more involved debugging to see more precisely where this overflow is occurring. Regards
  3. OK, Pete, I'll try zapping those pesky joystick sections from the FS9.cfg Understand about letting FS9 rebuild it, but I have probably 3-4 man-weeks invested in tweaking the blasted config, and am less than cheerful about the idea of re-mapping the FS9 genome... :wink: Cheerio
  4. Pete; I tried disabling the joystick and got an even worse storm of registry thrashing. Understand that PFC does nothing with the joystick...but I did think it important for PFC users to know that if using a PFC flight control with no joystick attached to the PC (I mean with a PFC unit at one's disposal why *would* one want a joystick on the PC?), FS9 will still be busily looking for a joystick in the background even while it's getting control inputs from the PFC driver via FSUIPC. My rather inelegant solution is to plug in a cheap joystick as a sort of FS9 pacifier. If you give Bad Billy what he wants, he shuts right up. I didn't know if (but was hoping) you had some wizardly way to head off DirectInput at the pass...as you often do with these things. Cheers
  5. Pete; Was watching FS with Mark Russovich's RegMon utility, and noticed a steady stream of unsuccessful hits for joystick settings on a registry key for DINPUT.DLL (see screenshot). Hit frequency was something like 30-50 times a second. I use a PFC yoke and throttle combo without a regular HID joystick connected to the PC. After seeing this registry thrashing, I plugged in a USB joystick in addition to the PFC combo, and disabled all the axes of the USB joystick in FS9. The registry thrashing stopped, and frame rate excursions have smoothed out some. Not sure there's anything that can be done in the PFC driver, but it's a curiosity worthy of a look. Cheers
  6. OK, well then I'd be looking hard at something like an IRQ or address conflict. Make sure the USB adapter isn't using the same I/O address as the onboard ports, or that there aren't two devices trying to be the same serial port. I've found that serial I/O does not always coexist peacefully with other devices doing interrupt-sharing, even though Windows PnP seems to think it should. Have you tried other serial devices on the ports in question...like a modem, perhaps? Cheers
  7. I'd start first by reseating both ends of the cable, and if that doesn't work, then try a different serial cable. If that doesn't do it, try monitoring the serial port with a simple terminal program. Otherwise it's probably time to send 'er back to PFC. I like your sound sets, BTW. Cheers
  8. Hi Pete; The LDS team released an SDK with the 767 add-on which gives access to a variety of extern variables, including one with the A/T state (via an IPC DLL they provide for their panel). If you don't have it already, hopefully a member of their team will provide it to you shortly. Cheers
  9. I could envision a few uses for such a beast... Cheers
  10. Lots has been written in the F1 ATR forum on the interaction of FS throttle inputs and the auto-torque on the F1 ATR. For the F1 auto-torque to work, the throttle input needs to be at 0 (idle). Any throttle movement...even the fidgety back-forth drift caused by a noisy pot, will cause interference with the panel's auto-torque control. That, unfortunately, is a panel programming characteristic, not an FSUIPC problem. I got around the prop beta (reverse) problem by assigning reverse to a separate lever on my PFC quadrant. Probably not an option on the CH unit. Regards
  11. Interesting...but what's it used for? Are you building a sim with real avioncs boxes? Sounds kinda expensive... Cheers
  12. The keplerian elements that describe the orbits of the 24 GPS birds are readily available in multiple venues on the internet. It's a relatively straightforward process to compute the azimuth and viewability of the sats for any given date/time (epoch). But...that said, it's a lot of computing power being devoted to a really esoteric piece of background data that one would almost never look at in real day-to-day ops. Regards
  13. Hmmmm...a set of offsets for "user head position" could be very useful, indeed. That way, when somebody sends in a log file with a problem with an FSUIPC-enabled program, the support staff can first check to see if the head position offset indicates that the user's head position is "up his... OK...never mind... :mrgreen: Just a spurious thought... Cheerio
  14. All three of the airplanes you listed are actually fitted with spoilerons, which behave exactly as you describe in real life. In the aircraft.cfg file, under the airplane_geometry section, there is an entry "spoilerons_available" When set to 1 it enables this type of flight control action. So if's there, it's because the FDE designer put it there. Regards
  15. Hi Pete; Actually, the takeoff thrust setting on the 727's center engine is always a tad higher than 1 & 3 because the bleeds are shut off on that engine. Use of asymmetric thrust to aid in ground handling on a jet with tail mounted engines isn't particularly useful. Anyway, absent abrnomal circumstances, having the two outboards slaved together and the center separated does make some sense. Cheers
  16. Hi Pete; Along these lines, also an option to map one lever to throttles 1+3 would be helpful for 3-engined birds. Right now with a 2-throttle quad, you have to do 1+2 and 3. Cheers
  17. Try running DXDIAG also...go to windows start -> Run and type "DXDIAG" in the window. It'll do some basic testing on your drivers w/r/t DX. Don't know what the SIS utility is, but anything flagging a memory error with the kinds of problems you're having calls for a closer look. Did you run memtest86 as I recommended? I've found that utility to be very good at finding physical memory problems. It also might be worth swapping the two memory modules as well. Regards
  18. Howie; It's very unlikely that the drivers which came on the CD for your video card are up to date. Win XP SP2 includes an imbedded update to Direct-X 9.0C, and many older drivers have big problems with the new version of Direct-X. Recommend you update with a recent version from http://www.guru3d.com or the nvidia website. WinXP SP2 also included many changes to networking components, and it's possible your LAN drivers aren't current either. Likewise, the Soundblaster 2 drivers should be updated from the Creative website. I'd recommend you find a memory check program like Memcheck86 (http://www.memtest86.com) and run it for several hours to see if there's a problem with your RAM or some other part of the memory subsystem. Also, the freeware program MBM may help in resolving the temp indication issues. Most CPUs have more than one thermistor, so varied readings can happen, but not usually by that much. Also see this article: http://www.vanshardware.com/articles/20ttling.htm A hot spot on the CPU could cause the hardware to throttle the CPU, with the possibility of system instability. A hot spot is easy to create with less than fastidious attention to heat sink bonding. Or...also possible is a CPU with a faulty thermistor. Honestly, my less-than-fully-informed guess would be a driver problem...but the odd CPU temp readings are a troubling sign that needs a closer look. Good luck
  19. The short answer: FS does not perform any meaningful simulation of engine vibration for any type of engine. Values produced (for jets only) are notional. The prop amp indication is an equivalent to the engine vibration readings in a jet engine. The prop amplitude is a measurement of the peak amount of vibratory motion per unit time, and is proportional to the magnitude of the mass imbalance on the prop assembly. Resonant vibratory stress becomes a problem if either an excessive mass imbalance is present (prop/gearbox/engine is not balanced properly) or also possibly by the resonant effect of the regular power pulses applied to the prop by the power-stroke detonation in each cylinder of a reciprocating engine. This explains why some recip powered aircraft have ops limits which prohibit sustained operation of the engine in certain RPM ranges that produce this power pulse resonance. That said, modeling of vibration response of a particular recip/prop combo is well, well outside the bounds of what MSFS will do. It'd be an interesting add-on feature. Cheers
  20. Pete; Last night my car started making this kinda funny ker-chunky sound, with a little bit of high-pitched wheezsazz noise at times. At the same time, my son's GameCube started randomly re-booting, usually right around the time I told him to head for bed. I usually flash the lights at him, and I think the GameCube may be plugged into the same socket as the lamp. These two events certainly cannot be coincidences. I have four college degrees, and wrote a computer program once, and I feel sure that it must be a bug in FSUIPC. Fix it or else!! :lol: Cheerio Bob
  21. SBRelay must be run on the host PC. SBHost and SquawkBox both run just fine on a client PC using WideClient in lieu of MSFS. Regards
  22. OK Pete. Nothing as ominous as stolen keys there. Looks more like they've written an add-on panel that may not coexist with the most popular add-on utility in FS-land (FSUIPC) and choose to suggest that people now need to contact you to resolve the perceived incompatibility with their stuff... Personally, I'd rather be able to use ActiveSky, FDC, Squawkbox, and my PFC flight controls than use their panel anyway. Cheers
  23. Pete; Might be a good idea to have a look in the FeelThere forums...their developers seem to be quite content to quickly point their fingers at FSUIPC as the root cause of a number of their new add-on's problems. Cheers Bob
  24. I wrote a few netpipes test apps and noted the same...widely variable lag and jitter. It was unuseable for any real-time IPC needs. Regards
  25. Pete; Please accept a monster-sized thank you for the dual-protocol support in the latest WideFS! The road has been rocky since the switchover from IPX to TCP/IP several years ago. I had, over time, stabilized things into a reasonably smooth system, but the recent combo of Win XP SP2 and all the networking changes it brought, then FS9.1, and then a motherboard failure, threw everything out of whack again, and I have simply not been able to get it under control. Though FS was clearly writing a steady stream of packets, they were arriving to the clients in bunches, with surging and ratcheting readily apparent all over the distributed system. I think there are simply too many processes that touch on TCP/IP control, due to security, internet throughput and other issues. To make a long story short, I installed IPX on my two Win XP Pro machines, and in a few minutes I had a near-perfect smooth flow of data. Coupling FS 9.1 running at 30 fps with the latest Project Magenta builds yields the best performance I've seen on a distributed FS system ever. I can't imagine ever going back to TCP/IP...hope you'll continue to support it in WideFS. Cheers
  • 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.