Raymundo

Sure thing, does it every time for me. Quite sure it has always done that since FSX. Guess its another fix for LM to do,but I am not too sure it will be very high on their list. :wink:

Gues its not a forum as such but on their website they have a Support page which provides some answers and the capacity to contact the developers directly. Worked super for me. Not many developers that invite you to contact them directly if you need help!! :smile: Would be interested in what you might find out if you would be kind enough to post it. Thanks and have a good day. R.

Not sure of the absolute correct answer myself, but, did you post this on the Real Air website/forum? They are really good about answering questions.

Not a bit of change here with three windows undocked. Using i5 @ 3.4 and an Nvidia 650 Ti Boost!

Shouldn't LM be able to tell you on their Forum? They are quite good at answering questions about their licensing requirements.

Open your default flight. Put yourself in the VC then save the flight using the semi colon and overwrite your saved default and the next time you open it you should be in the VC!

You will find FSUIPC in the "Add Ons" section of the Menu Bar.

Bermuda Triangle maybe?

If you use FSUIPC for your controllers then you should use a key press for F2 and be sure to tick the "Repeat while held" box.

What effect???

When I go into the P3D Flight Planner to load a previously saved plan it does not load the waypoints saved in the original on the first attempt, it only gives a Direct To version of the plan. In order to get the planner to load in the waypoints I had used, I need to clear the plan then Load it again. Is there a fix for this, or is there something I am doing wrong? R.

Frooglesim did a review on this this past week. You can likely find it on UTube

Yes, indeed, very, very misleading!

Did you post this on the Pete Dawson website? He is usually quick to respond to posts withe problems?

The commands you are using work fine for me in V3.1 to raise and lower the eyepoint. Two questions: 1. Are you using FSUIPC? 2. Are you running any add-ons such as EZDock or Opus FSI? r.

Not withstanding the rather unlikely possibility of malfunctioning equipment being the issue, if you are using FSUIPC then make sure you do not have "Enable Joystick" checked in P3D. Also to make sure of no interference from the sim, I have deleted all axis assignments in P3D. Throttle quadrant works ok with things this way.

Many thanks for your many helpful responses. Love the fact that simmers are always ready to help/share. Merry Christmas all. Raymundo

Does anyone have a smooth working profile for Track IR 5 that they might be willing to share? It would really be appreciated!

Yup, had the same thing happen but have no idea of how or why it did.

P3D does allow you to have outside views from all angles as FSX always did. The camera view "Outside View" gives you this ability.

I posted this on the P3D Forum but since its a weekend I thought I would see if anyone here might have an idea of what is happening. Up until lately, 2.5 has worked perfectly. Currently I am faced with some weird unexplained behavior. When I open V2.5 I sometimes get a pinging noise, as if I were holding a key down. If I open an application such as Plan-G or FS Cloud and there is a text box open, the computer then fills the box continuously with the letter "n" and I can't run the program at all. Ironically sometimes I can get past it and I'm ok. I had a backup copy of my .cfg file so I replaced the existing one to no avail. I also deleted the shaders, no go. I am using Win7 and have both 2.5 and 3.0 installed and this does not happen when I run 3.0!! Thanks in advance for any input. R. EDIT: Problem solved. It was a key press in FSUIPC that was checked to repeat! My own darn fault. As we always say at our Flight Sim Club, "it's all in a setting"

Rather rude post, I should say! If you read his post it only deals with one topic; his monitor issure. "Focus:!

Have you opened to see what the log.txt file says. I was getting this message and found it was being caused by an aircraft I installed myself. Simply removed the offending files and now the world is right!

If it hasn't happened, then why post it?

Super..thanx.