
LukeFF
-
Posts
400 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Posts posted by LukeFF
-
-
Thanks guys - I've not tried again, but I did use the Layout Manager tool suggested on Discord and that fixed the problem. 🙂Â
-
I downloaded the scenery this morning and enabled it through my mods manager and deleted the default one before starting a new flight, but the new scenery isn't showing.Â
-
2 minutes ago, kevink817 said:
Xbox or PC? What version?
PC
-
Hmm...it might be worth it then to make that more clear on the store page, as it says: "Custom maintenance functions: Engine oil levels, APU oil level, Hydraulic fluid level, wheel brake wear and tire wear." That makes it sound like it's more than just visual, and I know all along people on various sites have been under the impression that it physically changes the performance of the plane.
-
1
-
-
On 3/3/2024 at 12:20 PM, Nico - Gumby said:
What exactly do you mean with Manual mode? I'm not aware that the FMC has a manual mode.
When we reached the next waypoint, instead of continuing on towards the next one we starting flying around in circles. It was then I realized the plane was no longer in heading or nav mode and needed to be manually steered back on course.
-
I'll try to remember the next time I see it, yes.Â
In the meanwhile, it's the text in the DME readout area - it looks like a Z-fighting issue, where multiple layers of numbers are trying to be rendered at the same time.
-
On 3/3/2024 at 3:16 PM, Nico - Gumby said:
Sounds like you nearly stalled and THR L activated. But without a video / screenshots it's difficult to say.
Maybe, but it's been so long now I don't remember. 😄 But I've made a mental note to keep an eye out for problems with this in the future.
-
When starting a new flight from your typical parking spot, there is typically an excess of ground service equipment around the plane - 2 GPUs (the one that spawns by default with the plane, plus the one that is part of the airport scenery), etc. If the player is using GSX, it would be nice if these "extra" pieces of equipment would be culled out somehow so there isn't this cluttered mess when I start a new flight.
-
The other problem with this is that when I look for an available parking spot, all spaces are listed as too small. So, while I've disabled the message from appearing, this other problem remains.Â
-
After I activated my secondary flight plan and reactivated NAV mode, the FMC went into Manual mode when we reached our next waypoint. I had to input a Direct To Waypoint procedure to get us back on course. Is that how it should be?
-
In both aircraft.cfg files, there is a typo in the following line:
icao_manufacturer ="Aibus"
-
I've noticed the following buttons have no associated sound with them:
- Glideslope warning test (just to the right of the captain's altimeter)
- The VHF 1-4 buttons on the pedestal
-
I've noticed in some videos that some people have inHg on their EFB takeoff performance page, while I cannot get it to change from HPA to inHG via the Settings screen. Is this issue still being investigated?
Â
-
A few of your temperature knobs are set almost all the way to the Cold setting.
-
When landing at KMEM on runway 27, I received no DME signal from the ground. The frequency is supposed to be 108.7, course 273 degrees. Could someone check and see if it is working properly or if something is indeed wrong with it?
-
I have had at least nine CTDs in a row tonight trying to load the freighter version. This is beyond frustrating:
QuoteFaulting application name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x00000000 Faulting module name: mf3055c24e74fe5af_0.dll, version: 0.0.0.0, time stamp: 0x65e12e6c Exception code: 0xc0000005 Fault offset: 0x0000000000e0bcd4 Faulting process id: 0x0x4D60 Faulting application start time: 0x0x1DA6C5D81B30E19 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.36.2.0_x648wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Users\Luke\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\inibuilds-aircraft-a300-600\mf3055c24e74fe5af_0.dll Report Id: 9ed9cf54-8927-4a25-af44-dec628106f51 Faulting package full name: Microsoft.FlightSimulator_1.36.2.0_x648wekyb3d8bbwe Faulting package-relative application ID: App
Â
-
So, what does it take to get a response from anyone here about this?Â
-
On 1/31/2024 at 4:26 AM, Nico - Gumby said:
I send you both a DM with a logging enabled version of the iniManager, please test with that one and if the issue is still persistend there, please DM me back the log 🙂
Would it be possible to get that too? I am stuck right now without a working version of the A300 and would really like to be able to use the new version this weekend.
-
I have to agree - this app right now is a piece of junk. It really shouldn't be that hard to download and install an update.
-
I tried removing it from my Addons Linker folder, and I re-ran the app. And...it crashed again after getting halfway through the update process.
This is not good, guys.Â
-
As the title says - I tried to update the A300 for MSFS today and it crashed twice, and now the third time it just sits there saying "downloading" and nothing happens.Â
-
-
Update: nope, it was me. 😄 All is working properly now!
-
1
-
-
Yep, it looks like an AAO problem, as the default keyboard bindings work fine. 😞Â
All sorts of problems after installing scenery
in Support
Posted
So, after I installed this airport yesterday, MSFS has suddenly decided I need all of these mandatory updates. What happened is the following:
After that, suddenly MSFS said I needed these mandatory updates and after I downloaded several gigabytes of them, I was told on the main screen there were essential updates I needed to add, even though my content manager shows no such updates needed and my game updated to the latest version.
Long story short, I performed a clean reinstall of MSFS and everything looked to be back to normal, until about 30 minutes later it started over with the same original problem. So, right now I am in the midst of reinstalling another 130 GB of updates.
So is it coincidental or would the uninstallation of the stock JFK cause all these issues?