richboy2307

Thanks suggestion is noted.

Thannk suggestion is noted but just for reference you can "right click" or "middle click" on the dial to auto-set current GW value.

As MD82 has said,

Both Rudder (Rudder Axis) and Tiller (Nosewheel Steering Axis) will control the nosewheel. That is how it is on the real aircraft as well and this is what is simulated now since v1.0.4
The difference between the two is in the degree of travel. The rudder alone has limited movement of nosewheel, while the tiller can move the wheel much further/sharply.
So even if you set RUDDER CONTROLS TILLER to NO, you will see some limited nosewheel steering with rudder axis input alone. Then try giving tiller axis input (to either left/right extreme) and you'll note it goes much further.
If you're having any other issue, please provide video/screenshots of what you're seeing and also of your keybinds for both Rudder Axis and Nosewheel Steering Axis.
----
Moderation Note: I have deleted the irrelevant messages that had no bearing on the issue at hand.
Thanks!

Hey
Glad its sorted. For the benefit of other WinCtrl hardware users that may suffer from same in future, could you list exactly what was the issue and what you did to fix it?
Thanks!

The GNS530 getting stuck on initialisation is a sim bug as far as we can tell. It's all WT code and we're not doing much our side with it besides giving it power (without which the display wouldn't turn on at all).
If you do get stuck in this situation, you can as Jake suggested, try to recycle power (Trip the APU GEN or disconnect EXT Power) as that usually resets it. Alternatively you can try to restart your flight though that is rarely necessary.
This issue is reported on other aircraft using WT GNS as well and we're hopeful it will be resolved eventually.

Hey
Randomised from doors open to doors close on the ground
Random 10-15 mins after seat belt sign turned on above FL200
Randomised on ground after doors open again for arrival

Thanks, there were many different cabin configurations for the L1011, but the version we’ve modelled is based on the best references available to us. At this time, we don’t have plans to add additional cabin layouts, and we believe the existing variants already offer a good range of options to capture the feel of this era of aviation.

We're not seeing this our end. Try the following maybe?
If you locally installed the addon via My Library, try deleting and revert to streamed version?
Check under "My Library" if these liveries show up and are not "disabled"?
Delete your Content.xml file and restart the sim after to let it build fresh.
NOTE: This will reset any addons you may have previously disabled manually via My Library. Keep a backup of the original file and re-disable the addons after if needed.

Is a livery-side issue. Already reported elsewhere, the relevant livery artists will work on it when possible. Expect livery updates via iniManager or Marketplace Livery packs for this. Thanks!

This should be resolved as of 1.0.3 update, please let us know if not.
This is by design currently per reference documentation used, so it will sequence the next filled waypoint in AUTO sequencing. The only condition to this is that you have 3 or more waypoints in the INS in total.

Repaints (those obtained via iniManager) should not affect this as there are no files included that would affect systems logic. We can't say the same for all community-made liveries however.
Changes have been made in v1.0.3, so please let us know if this is still the case now?

Hi
There is a potential fix in v1.0.4 coming that may address the issue of the spoilers not appearing visually post landing.
Please verify and let us know after.
Thanks!

Hi
As of 1.0.3, the PMS behaviour was changed to show "888" when it cannot calculate any valid result. It is also actively using the current SAT value to determine OPT. As such, it will update in flight, particularly when current SAT updates to sensible values where a valid result can be achieved.
SAT of +40c at those weights won't net any valid results, hence the 888. Team is still investigating whether you can force a prediction on the ground, references we have are unclear but the behaviour currently is reflecting best the "known" reference logic.

Should be fixed as of EGGP v1.0.4 Update.

Hey,
The fuel jettison feature is currently in development and planned for a future update. It isn’t included in v1.0.3 yet, as noted on page 80 of the manual.

Interesting, internal testing reports are exact opposite but appreciate it. We also have further optimisations coming in v1.0.3 (potentially next week). Please check again and let us know.

With regards to degraded perf/stuttering, let us know if theres any specific conditions where you particularly notice it. Or any actions taken that trigger it.
Thanks!

Do you mean if you're spawning airborne somewhere in the sky (instead of on the runway or on a gate?). Could be an issue with the panel state its trying to load in that instance, we'll have a look.
I would recommend disabling all 3 crash detection from Settings > Assistances. They usually cause conflict with 3rd party addon systems. 
 
Thanks!

1. The LTN-72 is not capable of triple-mixing IRL, so not simulated by design. The AP on this equipment configuration can be driven by INS-1 or INS-3 only. At the moment, only INS-1 drives the autopilot in the simulator. Team is investigating feasibility of coupling INS-3 in a future update.
2. Remote functionality is planned for a future update.
3. INS-Drift is simulated, and is a user-configurable option via the PFB Aircraft Settings (Note: Further refinement of drift-rate is in progress).
As MD82 mentioned above, there is no automatic position updating on the LTN-72 (manual excerpt attached). The manual position-updating procedure is explained starting Page 105 in the manual which can be obtained here.

For the upcoming v1.0.1 update, we’ve made adjustments to the tint. Once the update is available on the Marketplace (expected around next week), we’d really appreciate it if you could try it out and let us know how it fairs.
Correct, the simulator doesn’t factor that in when determining interior brightness. The noticeable contrast between the interior and exterior is mainly due to how the sim currently handles eye adaptation, which is still a balancing limitation. The main workaround would be to brighten the cockpit textures, but that introduces much greater inaccuracies in the overall colors, so it’s a difficult trade-off.
 
Thanks!

Hi @GACSavannah
Check that your simulator paths are set correctly in iniManager. Click your name at the top left, choose 'Sim Paths' from the menu. Use the 'Scan' button to set a path automatically or click the 'Folder' button to pick your community folder manually.
Then, restart iniManager and try again. 
 
Alternatively, you can also grab third-party liveries from external sites like Flightsim.to for example.
Thanks!

Thank you for your suggestion. We are currently exploring the possibility of integrating your OFP flight plan for preview within the Enroute page of the PFB.

Re-download the latest version of this livery via iniManager.
|It correctly shows under PW Freighter variant and engines only.

Thanks we believe the following liveries were affected by this issue and updates have been pushed, Please update or re-download these liveries from the iniManager:
[GE] Air France (F-BVGA) [GE] Lufthansa 'Classic' (D-AIAN) [GE] FedEx (N667FE) [GE] Emirates SkyCargo (A6-EFA) Thanks!

Hi @DDoBaGi

That looks like you have 2 Dubai sceneries active at the same time.
Please verify you have disabled any other OMDB sceneries from your My Library (e.g. Default handcrafted OMDB) 
See below article for how: https://flightsimulator.zendesk.com/hc/en-us/articles/17373373933340-How-to-enable-and-disable-content-in-the-simulator
As for Orbx Dubai Landmarks, OMDB Enhanced is not marketed as compatible nor is compatibility tested/supported.
That being said OMDB Enhanced comes with built-in Landmarks so would recommend disabling any other Dubai addons for the same.
Thanks!

Hi @LukeFF

Apologies for delayed response. But both of these are core-sim issues.
The sim adds a snow exclusion around roads (you can see this on the default LOWI as well) and currently offers no way to overlay or hide these roads as they're added in a layer above scenery by the sim, driven by their own vector data.
Same with Fauna (animals), these are dynamically generated by the sim with no way to create any exclusion zones for them. Only workaround for now is to disable them in the Graphics settings.
Thanks