Jump to content
The simFlight Network Forums

BC

Members
  • Posts

    20
  • Joined

  • Last visited

About BC

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

BC's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Pete, Got the update and it works swell! Perfect! I've forwarded the latest log and ini file for your perusal. Thanks again, BC
  2. Howdy Pete! I've posted an update to the F1 forum regarding the conflicting commands. It should be noted that if the ATC window is actually open, clicking the COM/NAV2 swap does in fact close the ATC window. I see what you mean about the archaic coding. You are right, the non-specific stuff went out with the DODO. I wonder how the F1 guys will respond. Seems a lot easier if they just update their code. I have a feeling that won't happen, but we can hope, right? Thanks again Pete, I'll buy you a fine pint at the next Squadron party! BC
  3. Pete, Looking through the log file I sent to you, there is a recurring theme: (0x00000000) COM_RADIO 481106 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 481107 *** EVENT: Cntrl= 65581 (0x0001002d), Param= 0 (0x00000000) FREQUENCY_SWAP 481107 *** EVENT: Cntrl= 66372 (0x00010344), Param= 0 (0x00000000) COM_STBY_RADIO_SWAP 481166 SimRead: 034E="COM ACTIVE FREQUENCY:1" INT32: 8592 (0x00002190) 481166 SimRead: 311A="COM STANDBY FREQUENCY:1" INT32: 10293 (0x00002835) 481166 *** EVENT: Cntrl= 65539 (0x00010003), Param= 0 I am not doing ANYTHING with ATC here, so where is that "ATC_MENU_CLOSE" coming from? All I did was change the frequencies and toggle the swap button. BC
  4. Pete, As you already knew, the log file is too big for here. I've zipped up both the log and ini files (as instructed) and they should be whizzing through cyberspace to you right now. BC
  5. Howdy Pete, Some background I should have included last night. Sorry for the omission. The AOPA Cardinal is a special deal that Flight 1 does every year for AOPA members. AOPA (The Aircraft Owners and Pilots Association) restores/rebuilds an aircraft every year and gives it away to one of the members in a sweepstakes. See: http://www.aopa.org/sweeps/ for details. For information about the F1 Cardinal, see: http://www.aopa.org/sweeps/fly/. You have to be a member to download it. Anyhow, Flight1 did a Commander and a Cherokee 6 for FS2004 and have now done the Cardinal for FSX. The Cardinal is supposed to be a brand new model, fully FSX compliant and as far as I know, they do not make use of FSUIPC. That would be evident to me as there are no problems with the airplane when FSUIPC is not involved. The airplane is not supposed to be a rebuild of the DF Cardinal. A gazillion years ago, I did some gauge design for the sim just for fun and for the life of me, I don't know how someone could mess up the frequency swap. I mean, it's a pretty basic function, right? What code could someone insert into the programming that would cause it do work normally without FSUIPC in this instance, but react completely different when FSUIPC is present? I know that you are extremely busy Pete, so don't go nutz over this. I was sort of hoping that there was a simple snip that I could place in the FSUIPC.INI file to sort this out. Evidently, it gets a little more complicated. I'll get the info you need into a log file and paste it here if it's small enough. Thanks and Regards, Bill (BC)
  6. Pete, Strange snag. I have downloaded and installed the AOPA Cardinal for FSX and the bottom line is that NAV2 does not work with FSUIPC installed. I can change the *frequency* in the standby window, but when I hit the button to toggle the frequency to active, it toggles NAV1 instead. I'm using FSX SP1 with FSUIPC v4.1.5.6 and PFC 4.3.0.0 FYI, I am using the Cirrus II console without the avionics. I have confirmed FSUIPC's involvement by removing the .dll and it's .ini file and running FSX, where the COM/NAV2 radios swap as advertised. Putting FSUIPC back in the modules folder and COM/NAV2 swaps COM/NAV1 when toggled. Every other airplane I have (stock and a few add-ons) work swell. It's only the Flight 1 stuff. I have posted on their site but have not received a response yet (it's been about a week). Any ideas? BC
  7. Hey Pete, Realized that I had an early version. Got the latest from Schiratti, (v4.09) and that doesn't work either. You have a plan, right? BC
  8. Pete, The patch is out and now nothing works! Strangely, everything tests OK in the FSUIPC /PFC test pages, but the sim doesn't recognize any inputs from my Cirrus II setup, which worked fine before the patch. I reinstalled FSUIPC v4081 before I started nagging, so what's up? BC
  9. Howdy Pete! I'm hoping you are going to keep that fix in the next update as GPS Out does not work for me AT ALL with FSX. I'm using v4.030 and it looks like your test version of 4.032 fixed the snag, at least according to what I've read here so far. Happy Contrails, BC
  10. Pete, I'm sorry about the poor choice of subject line in the starting post. Should have give it a bit more thought. I'll write something up with all the version info and send it on to you with the assiciated logs and ini files. I think you may be on to something with the wx file for the saved flight. Let me see if I can first duplicate the error (logged) and then I'll ditch the wx file and start fresh. On another note, things seem to go weird when I add a new airplane. Everything is fine until I set options on the PFC setup menu. If I load pfc without an ini file (fresh install) and do nothing except set the com port, things seem to work fine. Only after setting options/preferences. Anyway, I am sorry about my subject wording. Merry Christmas and all the best to you and yours, BC
  11. Pete, this ain't the time, Christmas and all, but there is another problem. FS2K4 crashes when I switch times, planes, whatever, with the PFC.DLL loaded. It's bad. Here is the error message: AppName: fs9.exe AppVer: 9.0.0.30612 ModName: weather.dll ModVer: 9.0.0.30612 Offset: 00011812 Here is a snip from the log file: ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=6018B72D[6018B72D] InitDelay: 0 seconds WeatherReadInterval=4 DebugStatus=255 2328 System time = 00:08:51 2328 \\IGRAINNE\IGRAINNE ©\Flight Simulator 9\ 2328 System time = 00:08:51, FS2004 time = 12:00:00 (00:00Z) 5984 C:\Documents and Settings\William Cullen\My Documents\Flight Simulator Files\Beverly.flt 6187 AIRCRAFT\Flight One PA-28\PA-28-181.air 22469 Advanced Weather Interface Enabled 22469 Traffic File #17 = "scenery\world\scenery\traffic030528" 55828 ClearWeather Button Pressed 56875 WeatherOptions set, now 6018B72D (timer=0) 57109 ***ERROR C0000005 at 21132556 ChainedProcFF 57109 *** Access violation trying to read address 00000004 57109 *** EAX 0171FF90 EBX 00000000 ECX 00000000 EDX 0171FF90 EDI 0000000E ESI 0176E804 57109 Stack -1 (01761F50) = 0042CB71, Bad=N 57109 Stack -2 (04D6DA78) = 00000002, Bad=Y 57109 Stack -3 (6E69614D) = 6E615020, Bad=Y 57109 ***ERROR C0000005 at 21132556 ChainedProcFF 57109 *** Access violation trying to read address 00000004 57109 *** EAX 0171FF90 EBX 00000000 ECX 00000000 EDX 0171FF90 EDI 0000000E ESI 0176E804 57109 Stack -1 (01850AD8) = 0042CB71, Bad=N 57109 Stack -2 (01850B88) = 00000005, Bad=Y 57109 Stack -3 (61666544) = 20746C75, Bad=N 57156 ***ERROR C0000005 at 21132556 ChainedProcFF 57156 *** Access violation trying to read address 00000004 57156 *** EAX 0171FF90 EBX 00000000 ECX 00000000 EDX 0171FF90 EDI 0000000E ESI 0176E804 57156 Stack -1 (01761F50) = 0042CB71, Bad=N 57156 Stack -2 (04D6DA78) = 00000002, Bad=Y 57156 Stack -3 (6E69614D) = 6E615020, Bad=Y 57156 ***ERROR C0000005 at 21132556 ChainedProcFF 57156 *** Access violation trying to read address 00000004 57156 *** EAX 0171FF90 EBX 00000000 ECX 00000000 EDX 0171FF90 EDI 0000000E ESI 0176E804 57156 Stack -1 (01850AD8) = 0042CB71, Bad=N 57156 Stack -2 (01850B88) = 00000005, Bad=Y 57156 Stack -3 (61666544) = 20746C75, Bad=N 57187 ***ERROR C0000005 at 21132556 ChainedProcFF 57187 *** Access violation trying to read address 00000004 57187 *** EAX 0171FF90 EBX 00000000 ECX 00000000 EDX 0171FF90 EDI 0000000E ESI 0176E804 57187 Stack -1 (01761F50) = 0042CB71, Bad=N 57187 Stack -2 (04D6DA78) = 00000002, Bad=Y 57187 Stack -3 (6E69614D) = 6E615020, Bad=Y 57187 ***ERROR C0000005 at 21132556 ChainedProcFF 57187 *** Access violation trying to read address 00000004 57187 *** EAX 0171FF90 EBX 00000000 ECX 00000000 EDX 0171FF90 EDI 0000000E ESI 0176E804 57187 Stack -1 (01850AD8) = 0042CB71, Bad=N 57187 Stack -2 (01850B88) = 00000005, Bad=Y 57187 Stack -3 (61666544) = 20746C75, Bad=N 57234 ***ERROR C0000005 at 21132556 ChainedProcFF 57234 *** Access violation trying to read address 00000004 Pete, I just spent the last four hours trying variations on a theme to rule stupid things out, but the bottom line is that FSUIPC and PFC are no longer getting along. I ONLY get the crashes when the PFC driver is loaded. EVERY time the sim crashes, I get the weather message. A clue, I presume. hey, Merry Christmas! BC
  12. Pete, Seems there may be a problem with the Commander, AC680. There is a note on their web site/FAQ page that sez this: "1. Throttle sync issues: After starting individual engines, throttles are not sync'ed or only one engine throttle is active. Use FSUIPC HOTKEYS to assign one key to re-sync the throttles. It works beautifully." Well, I have the opposite problem. Seems their gauge/model takes away my independent control. That would explain why the throttles work fine under the PFC menu but fail in the sim when the aircraft is loaded. Still don't know why the throttle goes to idle. Guess an e-pistle to the designers of that model are in order.... Come to think of it, FSUIPC is not required for their aircraft, so you shouldn't have to use your program to fix their model. I'll point that out to them. Thanks, BC
  13. Howdy again Pete! Strange that the mix and prop changed at all as I never touched them, they were at full for takeoff! I don't know where the setting for sync is in the pfc driver/menu. I am almost 100% certain it isn't set on the panel as there is no provision for it. Something is making my multi axis quadrant act like a single axis quadrant and I don't see where I could be doing it by mistake. Very strange indeed! I'll drop you a line and try the "fixed" pfc file, but first I'll see if I can duplicate the snag and THItime, get a pfc log for you to check out. Not to belabour the point however, when the throttle is doing its weirdness, everything checks out OK in the PFC menu. When I go back to the sim, its a "single axis" quadrant. Ya know, don't go nutz over this just yet. Maybe it IS a panel problem, unlikely, but let me see if I can get this snag to occur in a default twin. Rule out any red herrings. Thanks, BC
  14. Howdy Pete. Just tried it and got the weird throttle action again. This time I captured the event in a log file. Here is the file: ********* FSUIPC, Version 3.125 by Pete Dowson ********* User Name="removed by me" User Addr="removed by me" FSUIPC Key is provided WideFS Key is provided [Continuation log requested by user] Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=601CB72D[601CB72D] InitDelay: 0 seconds WeatherReadInterval=4 LogExtras=1 1227984 System time = 12:04:11, FS2004 time = 12:03:04 (21:03Z) 1227984 *VIS* SM: Min=0.00, MaxRny=10.00, MaxOvc=20.00, MaxCld=20.00, MaxClr=60.00, Upper=60.00, FT: LwrAlt=6000, UppAlt=25000 1227984 WeatherOptions set, now 601CB72D (timer=0) 1227984 LogExtras changed, now 1 1228031 READex 0609, 1 bytes: 00 1228062 AP READOUTS: Flags1=00000000, Flags2=00000000 1229015 READex 0609, 1 bytes: 00 1229015 READex 0609, 1 bytes: 00 1229015 READex 0609, 1 bytes: 00 1229078 READex 0609, 1 bytes: 00 1229078 READex 0609, 1 bytes: 00 1230922 READex 0609, 1 bytes: 00 1234125 READex 0609, 1 bytes: 00 1234281 READex 0609, 1 bytes: 00 1234375 READex 0609, 1 bytes: 00 1234375 READex 0609, 1 bytes: 00 1234515 READex 0609, 1 bytes: 00 1234515 READex 0609, 1 bytes: 00 1234515 READex 0609, 1 bytes: 00 1234515 READex 0609, 1 bytes: 00 1234672 READex 0609, 1 bytes: 00 1235281 READex 0609, 1 bytes: 00 1235281 READex 0609, 1 bytes: 00 1235328 READex 0609, 1 bytes: 00 1235375 READex 0609, 1 bytes: 00 1235515 READex 0609, 1 bytes: 00 1235625 READex 0609, 1 bytes: 00 1238500 READex 0609, 1 bytes: 00 1239406 READex 0609, 1 bytes: 00 1240172 READex 0609, 1 bytes: 00 1240172 READex 0609, 1 bytes: 00 1240218 READex 0609, 1 bytes: 00 1240265 READex 0609, 1 bytes: 00 1240265 READex 0609, 1 bytes: 00 1240593 READex 0609, 1 bytes: 00 1240672 READex 0609, 1 bytes: 00 1240765 READex 0609, 1 bytes: 00 1240875 READex 0609, 1 bytes: 00 1254484 READex 0609, 1 bytes: 00 1254484 READex 0609, 1 bytes: 00 1254484 READex 0609, 1 bytes: 00 1254484 GetRealAddr(24000D72)=01852D7A (orig 2EC8) 1254484 WRITEex 2EC8, 2 bytes: 00 00 1254484 GetRealAddr(22000034)=61049214 (orig 0890) 1254484 WRITEex 0890, 2 bytes: 00 40 1254484 GetRealAddr(2200003C)=6104921C (orig 0928) 1254484 WRITEex 0928, 2 bytes: 00 40 1254484 GetRealAddr(22000044)=61049224 (orig 09C0) 1254484 WRITEex 09C0, 2 bytes: 00 00 1254484 GetRealAddr(2200004C)=6104922C (orig 0A58) 1254484 WRITEex 0A58, 2 bytes: 00 00 1254484 GetRealAddr(22000032)=61049212 (orig 088E) 1254484 WRITEex 088E, 2 bytes: 6A 3F 1254484 GetRealAddr(2200003A)=6104921A (orig 0926) 1254484 WRITEex 0926, 2 bytes: 00 40 1254484 GetRealAddr(22000042)=61049222 (orig 09BE) 1254484 WRITEex 09BE, 2 bytes: 00 00 1254484 GetRealAddr(2200004A)=6104922A (orig 0A56) 1254484 WRITEex 0A56, 2 bytes: 00 00 1277515 GetRealAddr(22000032)=61049212 (orig 088E) 1277515 WRITEex 088E, 2 bytes: A7 3D 1292234 LogExtras changed, now 0 Towards the end, I switched airplanes and the throttles were normal. Went back to the original aircraft and now OK. Ideas? BC
  15. Howdy Pete! I guess I painted that with a broad brush. I am using the Cirrus II console which I believe you are familiar with. The throttle sync box I was talking about is in the FSUIPC technical menu. Normally deselected as I don't need it with the console as I have the 6 lever quadrant. I also don't have anything on the gameport and I have the option set to avoid possible interference from the gameport in the fsuipc menu. When the No.1 throttle started controlling BOTH engines on a twin (and the #1 Prop and #1 Mixture controlling both engines), I started hunting around for the cause. Now, when this was going on, checking the throttle (prop, mix) action in the PFC menu, all levers worked as designed. Move #1, #1 moves. Move #2, #2 moves. Back in the sim, #1 lever was controlling both engines, the #1 prop and mix the same. So I looked to see if something went weird in the FSUIPC menu. The throttle sync box was unchecked, but I still couldn't get independent control back. So I selected it, exited the menu and then went back to the menu and deselected it. No joy. Then I switched airplanes and everything was fine. Went back to the original airplane and it too was fine for the rest of the session. This weirdness only cropped up in the past week or so. I am using the latest and greatest versions of FSUIPC, WideFS (both registered), GPSOut and advdisp. The other day, I was flying a Beaver (single engine) and that was the first time any weirdness appeared. The engine kept trying to cut out on me and I thought it was because I was screwing up my fuel management. I did not pick up on it at the time, but now I see, or at least I believe, that the throttle kept going to idle uncommanded. That is the other half of the problem. Spurious and uncommanded throttle to idle motion. Recycling the throttle lever gets it back, but only for a while. It's almost as if I have an evil co-pilot. In both scenarios, there is no autothrottle present or any airspeed hold available on the aircraft I was using. The Beaver and the AC560 Commander. It's driving me nuts as it only seems to appear at random. Last night after about 45 minutes, then OK for an hour afterwards. If I can reproduce the event, I'll capture whats going on in a log file and shoot it your way. Naturally, now that I raised the issue it will probably never happen again, right? Oh well, keep the faith! BC
×
×
  • 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.