Hitchhiker79

That was it! Oops! Thanks!

I can't seem to get the Darkstar to take off in the DLC mission even with trim up maxed out. Anyone else having the same issue?

Adjusted the dead zones, no joy. I will try disconnecting a reconnecting the controllers to see if that might work.

Look for "NOSE WHEEL STEERING AXIS" in the control options. Then move the twist when in detection mode.

I'll try that next but I don't think I have that issue with other aircraft.

Yes it's set up correctly and I only use the tiller on the ground. The problem started after upgrading to v1.0.1.95.

No issue before departure. I use Toolbar Pushback by AmbitiousPilots. Do you think that might be the culprit? The pre-planned pushback function seems broken (tug disengages half-way through the process) since the first Fenix update.

Since the first update of the Fenix A320, I have noticed that the aircraft wants to veer right after landing. This doesn't happen at touchdown, but once I start taxiing. Has anyone else experienced this? It doesn't seem to be a controller issue. I have NWS assigned to the twist axis on my joystick and don't use the rudders with the pedal disconnect function to steer the nosewheel.

Yes I've experienced this with Mount Rushmore. I hope it gets fixed.

Thanks for the heads up. I gave this a shot and it seems to work as advertised. I am happy with the purchase.

On my (not so up to date) system, setting the slider on the lowest setting resolved my blurries issue. I guess your mileage will vary. I would suggest testing with a light-on-resources aircraft in an area which you find is prone to blurries, while keeping all other variables (other than the tessellation slider) equal. I would also suggest setting it at the lowest setting first to see if there is any appreciable change.

Did you try reducing the tessellation slider?

Hey Ryan, Switching HDR on seems to alleviate the problem, particularly when used with the settings suggested in: http://forum.avsim.net/topic/465890-p3d-hdr-brightness-mod-bright-daytime-and-dark-night/ I never really liked the default HDR settings, but these settings make it useable.

Hi Ryan, I have a GTX 660Ti. I've never had this problem until P3D v2.4. It too suspect that it's a card setting/driver related issue. I'll flag it to LM, should a solution not be forthcoming. At least I know it's been observed by others with different hardware/settings.

I've been experiencing an issue, specifically a visual artifact in the sky (banding) as per the screenshots below. I've started observing this since v2.4 (no issues in v2.3 and earlier versions). The artifact tend to be more pronounced than what is depicted in the screenshots. The resolution is set to 1920x1080x32 in both Windows and P3Dv2. Any help to resolve this would be greatly appreciated. I should add that this happens with both default sky textures or with REX4 textures, but I'm convinced the problem isn't related to the textures.

Curbz, How are you getting nVidia inspector to work? I have followed a few of the setups suggested on AVSIM, including Rob's, but I can't get it to force/enhance AA for love nor money. I have a 660Ti.

Hi all, I've followed the several instructions recommended on this forum to get nVidia Inspector to force AA in P3D v2.4. I followed the several methods/settings to the letter, but to no avail. P3D v2.4 on my machine that sports a modest GeForce 660ti, "refuses" to comply. Would anyone know if this might be an issue with this particular card (that would be odd, I suppose), or of a sure-fire way to get Inspector to work? I've tried, but was not overly impressed with the results, and would rather opt for 2xSGSS, if I can get it to work. Any help would be greatly appreciated.

The LM developers have made great strides in getting rid of the glitches/anomalies with ground shadows, but I still observed some artefacts as reported earlier in this thread. Looks promising though.

Resounding 1, but (there is always a but), it would be nice to see a concrete "roadmap" towards the resolution of long-in-the-tooth problems with this platform that afflict some if not all simmers using this platform: The micro/0.5 second/[insert your neologism here]-stutters Blurries The dramatic loss of performance in the notorious black holes of the sim, namely the Seattle area, London, Milan (and potentially others) As of recently, an issue with aircraft carrier lights, and wake effect (I appreciate this is a niche request) These issues would be really great to resolve, and it would be great to see Lockheed Martin devote attention to these issues over and above eye-candy items that are usually found in their request list, like sloping runways, etc. But then again my interests/priorities as a simmer are probably different from their commercial goals/imperatives/etc. Just my unsolicited 2 cents/pennies.

The SSW Harrier is highly recommended, as are all other SSW models. The flight dynamics are very convincing and have been tested by real world Harrier pilots. The transition from VSTOL to regular flight and vice versa works very well. Additionally, the SSW Harrier, as well as all other SSW models, will benefit from a virtual air combat module that is currently under development.

I don't think this correct. What you describe is flight envelope protection, not FBW per se.

Workaround here: http://forum.avsim.net/topic/381121-realair-lancair-legacy-in-p3d/

issgazer, many thanks for the workaround! Shame you have to faff around to get it to work fully in P3D, but at least it does! The workaround also works for the Duke soundpack!

I am trying to get in touch with "bliksimpie", the author of the sound pack but the messaging system says he is unable to receive PMs... Is there anyone who uses this sound pack who can confirm if this works in P3D? Thanks!

The Duke per se works fine, but the sounds for switches/knobs from the soundpack are not being played. Perhaps it's only happening on my system?