For those who haven't noticed...

[Paul K]

Never had that problem Paul.

No, it seems to vary with set-ups Ben, and nobody can pin down the actual cause. LM originally thought it was due to the HDR lighting being enabled or certain Nvidia drivers - but even with those eliminated, it still happened if the aircraft selection screen was enabled at start up. Anyway, they say they have fixed it. More interesting is the discovery of the historic bug that was responsible for the micro-stuttering that plagued FSX from day one - that really is a major fix. P3D will be sorted out before the F-35 at this rate.

[Scorpius]

Re: For those who haven't noticed...

Postby Chris558 » Fri Jan 03, 2014 21:05
Hi Guys.

I've had P3D running a few weeks now, and it's running pretty good with Horizon's photo scenery. I must say though, I'm not keen on the user interface, as when you start, it takes you straight to the Aircraft on the runway, before you can make your settings. Anyhow, I have a few issues I've so far been unable to resolve. I haven't been bang up to date with this thread, so sorry if any have been covered already.

Firstly, every time my flight loads, the Aircraft's throttle is open and the damn thing has left rudder engaged resulting in a left circuit on the runway! ...how can I stop this?

You need to remove all the axis associated with the rudder, elevators, ailerons and throttle and ensure that it is only the rudder pedals that are assigned to the rudder, this fixed the problem for me.

Nev

[J0hn]

Sorry a little OT - my upgraded PC is now ready to go (but only 8GB of DDR3 instead of 16 - order mistake on my part), but I was horrified to find that the GTX760 only has one 'proper' DVI slot, so I can't connect my second monitor. I tried living without a second monitor before in FSX and DCSWorld and it was horrible, so I know P3D will be the same.

It has what looks like a DVI slot, but the four pins - two either side of the spade bit - are not catered for, so a standard DVI plug is useless.

Fortunately, my new motherboard has integrated graphics, so I hope I will be able to use the VGA socket and run the two alongside each other.

This is awful!

Still going to take a few days to get P3D up and running, though, and I'm already suffering severe withdrawal symptoms after just a week without I'm wondering if I'm going to have to send off my terrain config file again for optimisation with the night lighting textures I bought. They already did that with it for FSX, though not with FTX scenery installed. Reinstalling and optimising is turning into a major operation - even more so than in the past, with FSX alone.

PS - get this - I installed Win7 64bit from my original retail disc and the updates over internet totaled several thousand files!

[DaveG]

I had a similar problem when I got my 760. One connector is a DVI-I (digital and analog with the four pins you mention), the other is DVI-D which is digital only.
My secondary monitor is an older analog TFT which has to run through a converter plug, but that only fits in the DVI-I connector, which is the main output on the card, so when the PC boots up it uses the older monitor as the primary display. Luckily once Windows is up and running they get swapped over and all works as it should.

[TSR2]

John, you've got the wrong DVI cable mate. None of the current cards have both DVI connectors with the 4 pins. My 770 is the same, and no problem running my two DVI monitors with the correct cables. The 4 pins your taking about have been obsolete on DVI for years as its for DVI-I not DVI-D.

[GHD]

Many P3D users are complaining about anti-aliasing. Here is the AI Heron landing at Barra, it looks fine to me.

[TSR2]

I honestly think that lots of the "complaints" are due to folk over egging the sliders. I've a fairly modest card and don't have any AA problems. I didn't have any with the old 560ti either. TBH it was always the same when MS released a new version back in the day, loads of "complainers" but they actually made up only a tiny portion of the user base. Its the same with LM, if you look at the number of complainants, its fairly small compared with the overall user base (allowing for the issues they have already identified, accepted and are fixing.

[J0hn]

Thanks for your info on the DVI inputs, chaps. I spent the morning so far looking for info (wikipedia has excellent diagrams of all DVI socket variations).


Update:
Now and then, certain events remind me what a 24-carat plonker I can sometimes be!

In my efforts to get around this issue, I unplugged my main monitor DVI from the PC to find that it is a DVI-D plug! So, using the VGA to DVI-I adapter for my second monitor, as I always do these days, I don't need anything else and both plug into the GTX760 without any problems.

What a wally!

[J0hn]

Just a word of caution:

I installed P3Dv2 with all working well, using the Estonia Migration Tool to install many FSX add-ons to P3D.

I then installed FSX (having taken care to disable 'Virtual FSX' in the migration tool first) and it also worked just fine.

I then installed Acceleration and now FSX refuses to start. It crashes on every attempt, with no module named as causing the crash and the affected file being quoted as fsx.exe

So - do be careful. If it comes to it, I'll simply either ditch FSX, or use it with SP2 and ditch Acceleration (if SP2 works).

Alternatively, it might not be a bad idea to install both FSXa and P3Dv2, before installing the migration tool, if you intend to use it.

UPDATE: I tried again today - FSX works 'as is' and with SP1, but with SP2 it crashes. I've sent a support request to the Migration Tool dev to see what they have to say about it.

UPDATE 2: Okay - sorted by uninstalling the SPs in order, then running a repair from the FSX disc, then reinstalling SP1 and SP2 in order. simprop.dll had been reported as the culprit causing the crash and a repair is the recommended fix - and as seen, it works!

[GHD]

For the first time I have seen stars and the moon (with an enclosing rectangle) reflected on the sea. It is a fault with HDR lighting.