Jump to content
The simFlight Network Forums

Barbs

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by Barbs

  1. Hi Pete,

    Sorry for not including more detail. I guess I was after the short answer, either "that's a problem" or "that is completely normal" before investigating further. Thanks for that,

    I am using FSX with registered FSUIPC v4.854 (6th Sept 2012) and have WideFS enabled although I am currently not connecting it to anything. When I clear the INI and generate a new one though the ShortAircraftNameOK= is set to No by default.

    I will continue to investigate today with the latest beta and get you those files soon.

    Greg

  2. hi, THANKFULLY it worked!!!!!

    Shahdad, Sorry can you please clarify what "worked"?

    I have suddenly started experiencing this problem and am looking for a solution that does not involve going back to Win7. On Tuesday I completed a 1.5hr flight with no problems and now (on Friday) I can't even get through a preflight without the saitek controllers (yoke, pedals and extra quadrant) from disappearing from FSX. I too don't understand how this has become a problem when I have been running Win8 Pro since the start of November with no issues.

    Greg

  3. Hi,

    For some reason, having created a profile for a particular aircraft, every time I fly I have to go back into FSUIPC and reselect "Profile Specific", then check every axis. While this in not a huge issue, it's annoying to say the least. Then I noticed when looking in my config file that the same aircraft was mentioned several times (this is a new install and I only have a few aircraft installed at the moment but it seems that each time I select profile specific in FSUPIC it add another line in the config file for that profile, even though the aircraft already exists there. Is this normal?

    This is what I see in the ini file.

    [Profile.B737]

    1=Boeing 737-8FE VHYIM Virgin Australia Airlines Winglets

    2=Boeing 737-8FE VHYIM Virgin Australia Airlines Winglets

    3=Boeing 737-8FE VHYIM Virgin Australia Airlines Winglets

    4=Boeing 737-8FE VHYIM Virgin Australia Airlines Winglets

    5=Boeing 737-8FE VHYIM Virgin Australia Airlines Winglets

    6=Boeing 737-8FE VHYIM Virgin Australia Airlines Winglets

    Why would it add an aircraft entry all the time like this? Surely once is enough?

  4. I expect they use different camera definitions. The camera facilities in FSX are both a blessing (because they are so flexible) and a curse (because they are so flexible).

    And what FS control is that "right click menu" sending? Use FSUIPC event logging to find out.

    Sorry, i did not write FSX and I do not always know exactly what any FS commands do. As I said, I think the cameras can be reprogrammed by anyone, including especially aircraft add-on makers. Best way to determine which commands to use is to find out which ones do what you want, and FSUIPC logging can help. Alternatively, for add-on aircraft, maybe they provide documentation which helps with keyboard shortcuts or similar?

    Regards

    Pete

    Hi Pete,

    I don't see anything in the camera file that would affect the view angle as I am seeing it. I only see zoom settings. Any reference to view directions is in the panel configs but this problem is occuring on all aircraft.

    I tried logging the commands but only the buttons appear to be recorded. Selecting the different views from the right click menu doesn't show up in the log. Interestingly if I use the button assigned to VIEW_COCKPIT_FORWARD the view looks up in the air about 10-15deg. But if I then use the hat switch to look left or right, upon centering the hat switch the view looks normal.

    I am now completely lost.

  5. Hi,

    I have two buttons mapped on my joystick to switch between 2D and 3D cockpits. The buttons are mapped to "View Cockpit Forward" (66653) and "View Virtual Cockpit Forward" (66654). These have been working fine except recently I have installed a realistic view patch for the iFly-737 for FSX whih has changed some view options in the panel.cfg for that aircraft and the camera.cfg for FSX. These buttons now no longer give me a forward view like I had before.

    Upon loading the sim I am in VC with a reasonable view. If I use the button I have mapped to switch to 2D cockpit I am looking up into the air about 15 degrees. Then if I use the button to switch back to 3D cockpit, the zooming and field of view is not what I had before. If I switch views using the right click menu this problem does not occur.

    It might help if you could shed some light on what these two commands are using for their reference positions as it appears the eyepoints or something that these commands are giving are not being read from my new panel.cfgs.

    Many Thanks

    Greg

    PS: FSCUIPC.DLL v4.703

  6. Hi Pete,

    Hope you had a great weekend at your daughter's. :)

    I have a problem that I've had for a few months but have only now noticed it may be something to do with FSUIPC. It has to do with the wind gauge on some of my addon aircraft not displaying the current wind conditions. In fact it appears that the gauge is "freezing" or not updating when the wind conditions change. This will have the following effects....

    1. When on instruments the aircraft appears to be tracking incorrectly for it's given heading (eg. tracking to right of heading when indicated winds give a cross-wind from the right).

    2. When visual around an airfield the aircraft attitude required to maintain a xwind approach is contrary to the indicated wind conditions.

    Example: Today I was flying a right downwind to runway 16R at Sydney Intl in the Wilco A330. Winds on the ND were indicating 130deg/15kts and I was heading 340deg. The track indication was showing as about 347deg (or to the wrong side for the given wind reading). Now here's where it gets interesting. The VATSIM METAR and the Wx being injected from ASE was for winds at 220deg/24kts (which more appropriately explains the tracking indication). Also on final for runway 16R I had to account for a xwind from the right (220/24 again matching the METAR) when the indication was still giving a xwind from the left.

    So why do I think this has something to do with FSUIPC? Well I discovered today that by opening the FSUIPC window and closing it again, the wind gauge returns to where it should be. Then after several miles of flying it starts to disagree again, so I bring up the FSUIPC window again and it returns to normal.

    Boring stuff:

    FSUIPC is a registered version.

    Version 4.6.0.0

    FSX SP2

    Win7 64 bit.

    FSUIPC weather is disabled.

    Weather supplied by ASE.

    Happens with both Wilco A330 and another 737 that I'm beta testing. These are the only two aircraft I fly in FSX that have a wind gauge.

    If it was a problem with the addon I would have thought it would happen on one and not the other.

    Any ideas???

    Greg

  7. Hi,

    Since a recent re-install of my system (win7 64) I have not been able to get a button mapping to gear up/dn properly. The settings through FSUIPC work normally but when I go to raise or lower gear, the correct sound effect plays but the gear state does not change. To bring gear up or down I need to press G or use a mouse click and it works. This happens with both default and payware aircraft.

    Any ideas?

    Greg

  8. Hi,

    I just started using FSUIPC 3.50 today and on two out of two flights noticed that my winds from top of descent to landing were not changing significantly. That is I had winds at FL380 of 277deg at 59kts and on final approach this had not changed, when the metar and AS2004.5 were telling me winds of 100deg at 10kts. It happened again on my return trip.

    I have not changed any of the settings, just installed the new module.

    I have not tried reinstalling the old module but I will do that soon to see if the problem goes away.

    In the meantime, is there anything else that could be wrong?

    Thanks

    Greg

×
×
  • 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.