Hitchhiker79

Was not aware of that, thanks. I am interested in the Curtiss C-46.

I thought of doing it that way, i.e. reinstalling 2020, purchase what I need from there, then wait for the transfer. Anyone else tried this? Just seems like an unecessary faff.

Is it not possible to buy any of the local legends, originally published in MSFS 2020, that are currently in the Aviator pack on an individual basis? I have the premium deluxe edition and I am intrested in one or two local legends but not interested in buying the whole upgrade. There doesn't seem to be the option to do so in the marketplace in MSFS 2024. Any ideas?

The same computer runs both LNM and MSFS 2024.

Thank you. Followed these steps and pretty certain I supplied the correct folder paths in the settings, but still no joy.

I can't seem to get LNM to load the airports in the database. Is this still broken from the sim side or is it something I am doing wrong?

Thanks for the solution. I had the same problem and fixed the problem using suggestion. I don't understand why Asobo does things like this.

I have a 500 mbit connection with no issues with the connection.

MSFS 2024 barely loads to the main screen, and no flights can be started; has been like this for the last couple of days. I have seen reports of a similar issue by users in France and the Netherlands. Absolute shambles. Next thing Asobo or Microsoft will tell us is that they did not expect a high demand while most people are on holiday for Christmas.

I am trying to implement all helipcopter hardware bindings in SPAD.next instead of using the controller setup in MSFS 2024. So far I have only managed to bind the cyclic, but I am struggling to assign 1) the collective axis, 2) the engine throttle (grip) axis, and 3) the cyclic trim. I am using the information within the SDK https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/Key_Events/Helicopter_Specific_Events.htm, but I am having no joy. Any help would be greatly appreciated.

I have found that when you toggle the VR toolbar, it doesn't always appear, as reported here, but moving the mouse then triggers it to appear. I have been using this methog to avoid leaving the flight and re-entering. Sometimes the toolbar appears squashed/distorted, but at least useable. It is disappointing that VR has been left in the state that it has at launch, particularly when so many resources have been set aside for the arcade elements of the MSFS 2024.

Excellent write up. I have the same experience with the H125.

My "Official2020" and "Official2024" folders are empty. Has anyone else encountered this? Not sure whether this is the culprit or not, but I have been so far unable to load a single flight. Not one. I am stuck with a blurry globe. Any clue as to how this can be resolved? I have tried re-installing, and I checked that I am not enrolled in the tech alfa in the XBOX Insider app. I tried flushing the DNS, etc. Nothing seems to be working. In the meantime Microsoft and Asobo are nowhere to be seen in trying resolve these fairly major issues. Any help would be appreciated.

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/