ISSUE DESCRIPTION
Description of the issue:
I’d like to report several issues in Career Mode!
- First, during a VIP mission in Nice, it all started while taxiing on the runway — the blue guidance ribbon suddenly disappeared for no reason, right in the middle of taxiing!
Then, after takeoff, there were duplicated gate markings, and everything ended up disappearing again mid-flight! (See screenshots)
- I’m not very familiar with this aircraft, but during the flight I got a message telling me to descend to avoid an oxygen issue, and shortly after, I received a message saying that my plane had crashed! (I don’t know if this is a bug or if I need to configure something.) However, with other aircraft of the same size, I haven’t had this kind of problem. (FL230)
- There are also some incomplete routes (maybe that’s normal? See photo).
Similarly, in the U.S., during a private flight with a 737, I followed the route shown by the game, but mid-flight I noticed that the route on the tablet and the one actually flown by the aircraft were slightly different! (See screenshots)
- There was also a bug where I requested an automatically assigned flight level, and the game gave me FL210 , but then, about 15 minutes into the flight, it suddenly asked me to descend to 2,100 feet!
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Not Add-On (only FS SU 2)
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
It depends on the missions and the aircraft.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- Freight Charter Service VIP (in France) with PC-12 / RAW75 9 / Nice
- Private Charter Flight (US) / (Los Angeles)
- Route generated by the tablet
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using, if relevant:
2 JOYSTICK t16000
[PC Only] Are you using Developer Mode or have you made any changes to it?
NO
MEDIA
Nice :
USA :
[END OF FIRST USER REPORT]
1 Like
"Let’s continue with the ‘Career Mode is unplayable’ series! A short 4-hour flight! Ruined after just 10 minutes of flying! Reason: you flew over a restricted area ! (on autopilot) And I’m just following the flight plan provided by the game. 
1 Like
Have some more bugs, put it short list below:
- penalty for entering taxiway without clearance during landing
- completed missions not logged in pilot log and there for no passive income for the flight time (already in other bug report)
- penalty for no landing lights after atc tells you to contact tower while still at FL180
- some career planes are bugged. For me personal i loved the sky courier but it got a lot of bugs in SU1 and zero fixes in SU2 . Allthough there are plenty bug reports. Now my live is gone.
- mission steps are a bit buggy… some times it’s working perfect some times it doesn’t work at all but most of the time it is somewhere in between. SU1 was more consistant (not perfect but better)
- hold short after landing is most of the time an inventation for another penalty
- helicopter unclear where to land on the runway, again hit or miss… give the helicopters their own procedures and utilize helipads
- … fill up
1 Like
I no longer have the blue-ribbon markers since SU 2 update. Completely disappeared. Perhaps they turned it off by default? I’m not sure.
1 Like
Hi all,
You’re only supposed to put one bug per bug report.
Please see this post from Jayne earlier today:
2 Likes
Ok… need some spare time for that
I thought it would be nice to have it all already together
Yeah, it makes it difficult for multiple reasons, including:
- As Jayne said, when they mark the bug resolved, it’s difficult to know what actually got resolved.
- Any time the QA team gets a bug report, they try to reproduce it. Generally speaking, a bug report should have one bug reported, and any comments underneath should just be additional information needed to reproduce it, in order to help the QA team, or discussions on how to work around the bug, if possible.
- Each bug reported should have reproduction steps. I can’t tell the number of times I’ve seen someone give a bug report that I couldn’t understand. But then when I read the reproduction steps, I got it.
You may want to give Zendesk a try with some of your bugs. In my opinion, you’re more likely to have someone look at the bug report if you log it there. But I will say, the more documentation you can give, the better. For example, with the bug, “hold short after landing,” it’s helpful to know what airport this happened at, what runway it was on, what aircraft you were flying, and what mission. And if you have a video or screenshots of it happening, it makes it that much easier for them.
Good luck!
i am not familiar with zendesk but will try that
1 Like
