Renamed my community folder and installed World Update 8. Then installed all updates in Content Manager. Shut down the sim. Copied G1000 mod back into the Community folder. Installed all windows updates. Installed Nvidia update. Rebooted my machine. Relaunched the sim.
Took off from North Las Vegas airport in C172 G-1000. Using VR. Incredibly smooth graphics. Not much jitter. Really impressed.
Flew around Las Vegas for a bit. Performed a touch and go on runway 12R. Then requested full stop landing. Received clearance for 12R. Shortly after touchdown after a short roll, while applying brakes, it seemed like the nose wheel collapsed and the airplane flipped forward. The propeller was on the runway and the airplane was perpendicular to the runway.
I did notice that as soon as I touched down, the taxi ribbon displayed. I wonder if I collided with the taxi ribbon? I wouldn’t think so.
I’m running Windows 11 home with latest update. MSI machine with 32 GB ram and RTX 2080 Super. Had live weather turned on.
The SIM performance was great until I crashed into the invisible wall. Replay would have been awesome in this situation.
Side note: I have the Working Title G1000 mod. On my approaches, I kept hearing a voice telling me to Pull Up. Is that normal? I was on a nice easy descent rate. I wasn’t nose diving into the runway.
Ok, that’s the first time I have experienced that at this airport. I’ve flown into and out of this airport numerous times. Must be a change in this update.
I have experienced this issue while taxiing in Dallas I believe.
Unfortunately, it isn’t a problem with the airport. This is just something that sometimes happens. Your next landing on that runway might be fine or it might not.
Yes, I didn’t have any problem on my first landing. That was my touch and go. The second landing was when I hit the runway tear I guess. Thank you for pointing out the issue.
Hello,
I moved this into the Airports cagegory.
We ask people to use the bug template rather than delete it. If you see me log bugs in the forum, you will see that I use them 100% of the time.
There is a master bug for runway tears, but i would appreciate if you could edit your first post to include the following info:
The bug template. Here it is (click to un-collapse it)
Bug template
:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
>
Brief description of the issue:
>
Provide Screenshot(s)/video(s) of the issue encountered:
>
Detailed steps to reproduce the issue encountered:
>
PC specs and/or peripheral set up if relevant:
>
Build Version # when you first started experiencing this issue:
>
------
:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:
[wrap=template key="Topic_template"]
Do you have the same issue if you follow the OP's steps to reproduce it?
>
Provide extra information to complete the original description of the issue:
>
If relevant, provide additional screenshots/video:
>
[/wrap]
The name and ICAO code of the airport in the title, plus the runway. Where you departed from is not necessary for the bug. (I think you landed in North Las Vegas, which is KVGT, but I’m not 100 sure based on what I read.)
If you have a video, that would be best. But they are notoriously hard to reproduce. (Videos must be 5 MB or less, so low-res is best. Unless you want to post a link to an unlisted YouTube video or something.)
State if you had photogrammetry turned on. I believe this is caused by photogrammetry.
Specifically use the word “runway tear” in your first post for searchability.