Jump to content
The simFlight Network Forums

Carob

Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by Carob

  1. Holy crap, dude. I was only asking for a little help. Sorry I don't measure up to your predetermined IQ qualifications.
  2. But one number is for using the Cntrl key, which I don't want to use, and another was for the actual key. With a comma between then. I found that line in a post someone else had done for helping in a similar situation. I don't understand it. Is the comma mandatory? Can just one number be used? Is the syntax different with just one number? I'm not a programmer so have no idea what it's supposed to look like.
  3. I did. But can't figure out what the line needs to be to do what I want.
  4. I had looked in that manual but still wasn't sure what to put. That's why I posted here.
  5. The paid version is needed for that, correct? I don't have that. I was told this is for Cntl + X AdvDisplayHotKey=88,10 so I tried it and it worked. I just don't want to use Cntl + X. I have a button on the yoke to invoke the "`" key for the default ATC but am looking to use that button for the AdvDisplay window for use with RadarContact.
  6. Hello. Can someone possibly tell me what the entry would be to put in the FSUIPC.ini file to use the "`" key (default ATC key in FS9) to show/hide the AdvDisplay window? Or, can someone tell me what the line would be to just configure Button 1 on the CH Yoke to do the same thing? I can't quite figure it out from the manuals, etc. Thanks!
  7. Well it doesn't seem to be the drivers and I don't know what DirectSound is. I think all we're looking for here is a solution. Which nobody, in multiple forums, seems to know.
  8. Are older version of FSUIPC available somewhere? I don't see them on Pete's site. I'd like to try a couple of older versions ofr FSX to see if something broke in that along the way somewhere.
  9. Hello. I wanted to jump in here and say that this same issue is happening with my father's new Jetline system he just got. When FsRaas is running it shows connected. When taxiing to a runway FsRaas says "Approaching" and that's all. Different airports, different runways, different aircraft... that's all that happens. No other sound is heard the entire time. If everything is quit and started again, the exact same thing happens. Only the very first word FsRaas is trying to play is heard and nothing more. FSUIPC 4.937 with FSX. Using FSUIPC 6.995 with FS9 and it works fine there. I too am searching for an answer to this but so far have come up empty.
  10. This could be a little difficult to work on now. I was doing some work on my father's computer as I was visiting for the holidays. Unfortunately I am back home now (another state) but I will see if I can get this information and get back to you. It might be a little while (if at all) but I will see what I can do. Thanks for your help so far!
  11. So am I looking for a file called "SimConnect"?
  12. I don't even know what SimConnect is. Is this something new with this version? I don't remember ever hearing the name before.
  13. To late for that. I just installed SP2 yesterday.
  14. After looking at this a little more I have found that this problem only happens with version 4.2. If I put version 4.06 back in the menu shows up fine. Anyone have any ideas? Thanks!
  15. Hello. I'm hoping someone can answer this for me. I have installed v4.2 of FSUIPC into FSX but I am not seeing the Addons menu. Here is a copy of the log... ********* FSUIPC4, Version 4.20 by Pete Dowson ********* User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired Running inside FSX (SimConnect SP1 May07) Module base=61000000 DebugStatus=0 31 System time = 15:51:50 31 FLT UNC path = "C:\Documents and Settings\Phil\My Documents\Flight Simulator X Files\" 31 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\" 828 LogOptions=00000001 828 SimConnect_Open succeeded: waiting to check version okay 6188 Exception 5 "VERSION_MISMATCH", Ref 447, Version 0.60905: Open: SimConnect Version incorrect! 6188 Trying another version of SimConnect ... 6297 Now running with SimConnect Original 6297 SimConnect_Open succeeded: waiting to check version okay 6297 Exception 5 "VERSION_MISMATCH", Ref 447, Version 0.60905: Open: SimConnect Version incorrect! 6297 Trying another version of SimConnect ... 6406 Could not link to all needed SimConnect facilities 6406 Failed on SimConnect_CallDispatch for Message, return = 0xFF100020 21453 **** Retrying SimConnect connection**** 21453 Could not link to all needed SimConnect facilities [code 0] 36516 **** Retrying SimConnect connection**** 36516 Could not link to all needed SimConnect facilities [code 0] 51531 **** Retrying SimConnect connection**** 51531 Could not link to all needed SimConnect facilities [code 0] 66563 **** Retrying SimConnect connection**** 66563 Could not link to all needed SimConnect facilities [code 0] 81641 **** Retrying SimConnect connection**** 81641 Could not link to all needed SimConnect facilities [code 0] 97438 **** Retrying SimConnect connection**** 97438 Could not link to all needed SimConnect facilities [code 0] 101235 System time = 15:53:32 101235 *** FSUIPC log file being closed Memory managed: 2 Allocs, 2 Freed ********* FSUIPC Log file closed *********** I read something about security software making this happen but none of this is installed. Even the Windows Firewall is turned off. Can anyone tell me what I need to do to fix this? Any help would be greatly appreciated. Thanks!
  16. I read yesterday that programs like Active Sky tell you to disable the weather options in FSUIPC because they have their own. Is this not true?
  17. It related to the initial question. I guess my question was if I don't have FSUIPC then I don't get to see "blue skies above and mist below". Is that right?
  18. That 3rd one came right out of the FSUIPC documentation. Right next to the other two.
  19. Hello. I'm wondering if some can answer a quick question for me regarding the weather settings in FSUIPC and FS2004. I am thinking about purchasing this much talked about piece of software but would like to clarify something first. In the documentation it says... Smooth visibility changes works for all weather in FS2004. IIt introduces visibility changes gradually when selected. You can adjust the speed at which the visibility is allowed to change. (This of course does not affect sudden visibility changes caused by clouds). This option is defaulted off, and does not occur at all for FS2000/FS2002’s local weather (including downloaded ‘real weather’). Where it says "does not affect sudden visibility changes caused by clouds... What exactly does this mean? Does that just mean that when flying through a cloud you aren't going to see much for that second or two? It also says... On FS2004, the upper altitude of restricted visibility can be set by FSUIPC, for global and local weather injected by external programs. Is the built-in real world weather considered an external program? If not, does that mean that if I'm using FS2004's built-in real world weather that I will not get things such as... "when you climb out of it you get blue skies (or fancy clouds) above and around you, but still see the mist below." Any help would be apprecaited here. Thanks!
  20. That's what I was hoping. Thank you for the quick reply!
  21. Hello. I'm hoping someone will answer a quick question for me regarding FSUIPC. I haven't yet purchased the new version (I plan it) and am wondering if what I'm seeing is related to that. Here's my question... When having the new version installed into FS2004 I do not see the tabs across the top once the module is opened. All I see is logs and another one (can't remember). Is this normal? Will I have the rest of the tabs one it is purchased or am I missing something else entirely? Thanks very much!!!
×
×
  • 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.