The only addon I have installed is FTX Global 1.1. Anyone without this addon?

 

I have it........ but have not installed it into P3D yet, and I have the broken cursor / clickspot problem, so I don't think it's related to FTX Global.

Same here, no FTX. Reloaded and still nothing. rendered unusable................. Almost acts like a simconnect deal

I've had this happen a few times. Random planes, random location, full screen or Windowed. It remedied itself each time but there was no clear "ahh haa" moment of what exactly clears it up

Have you tried toggling fullscreen? 

Have you tried toggling fullscreen? 

 

multiple times

I had the click spot problem at first too. The solution for me was the same for solving the black screen. By starting P3Dv2 in WINDOWED mode and NOT full screen, both problems vanished for me.

 

Barry C.

I had the click spot problem at first too. The solution for me was the same for solving the black screen. By starting P3Dv2 in WINDOWED mode and NOT full screen, both problems vanished for me.Barry C.

That did not work for me .....

This happened to me as well. I had to delete .cfg file to fix the problem For me it seemed to occur only when I created a new default flight. As long as I allow the original default flight to load, I don't seem to have the problem.

 

 

Sent from my iPad using Tapatalk

This happened to me as well. I had to delete .cfg file to fix the problem For me it seemed to occur only when I created a new default flight. As long as I allow the original default flight to load, I don't seem to have the problem.

 

 

Sent from my iPad using Tapatalk

That sounds interesting cause i saved a flight as default flght before. Will try it this evening.

 

Thanks for the hint will report back !

Carsten

I had the click spot problem at first too. The solution for me was the same for solving the black screen. By starting P3Dv2 in WINDOWED mode and NOT full screen, both problems vanished for me.

 

Barry C.

 

I do this anyway, as P3D 2.0 won't even start, unless I launch it in Window Mode.

 

 

 

This happened to me as well. I had to delete .cfg file to fix the problem For me it seemed to occur only when I created a new default flight. As long as I allow the original default flight to load, I don't seem to have the problem.

 

 

This does sound interesting, as I too have saved a new default flight.... anything to get me away from that dang forsaken military jet that launches by default........ and I mean LAUNCHES, because mine spontaneously takes off and crashes, every load..... :lol:

I deleted my new default flight situation from the CFG (and referred to the stock default), and CLICK SPOTS ARE WORKING AGAIN! 

 

My virtual beer of the week award goes to Skeuler for suggesting this!

Yes, it works.

 

This bug seems to be present if you save a default flight different from the stock one.

 

If it is your case, do the following:

 

1) Delete (or comment out) the line starting with "SITUATION", in your Prepar3D.cfg

 

The correct line should be:

 

SITUATION=FLIGHTS\OTHER\Prepar3D

 

 

2) Activate the preview scenario window in your Prepar3D.cfg

 

SHOW_SCENARIO_WINDOW=1

 

3) Launch Prepar3D and select the scenario, vehicle, time and date, etc.

 

Try if now it works, and remember, don't save any default flight.

 

 

With luck, we could report this bug to LM.

Well, thanks for the hint!!

 

Now, I am trying to figure out where is the problem in the saved flight....

it's working !

 

Thanks so much !

 

@LM: Do your homework......

Well, try now this hint:

 

1) Open your saved flight with a text editor

 

2) Search this line in bold:

 

</Section>

        <Section Name="Window.1">

            <Property Name="Order" Value="0" />

            <Property Name="Active" Value="True" />

            <Property Name="Undocked" Value="False" />

            <Property Name="Maximized" Value="True" />

            <Property Name="Locked" Value="False" />

            <Property Name="ScreenUniCoords" Value="0, 0, 8191, 6143" />

            <Property Name="UndocCoords" Value="0, 0, 0, 0" />

            <Property Name="Title" Value="Virtual Cockpit - View 00" />

            <Property Name="CurrentCamera" Value="{C95EAB58-9E4A-4E2A-A34C-D8D9D948F078}" />

        </Section>

 

3) If it has the value "True", change it with a "False", then save the file.

 

4) Open your saved flight and check it it works.

 

It worked for me.