All Activity

Experiencing exactly this; she feels very 'light' while on the take off roll.

Can confirm; clickspots on the overhead panel are a pain, after installing SU5.

I was well into my flight. I switched from Nav to VOR. As soon as I touched the VOR tuning knob, I got a CTD. This is build 1.0.10

Plane spawns in the air before falling to the ground and wobbling around for 20 seconds. At take off speed only the front wheels lift making it un flyable? Iv’e just purchased a plane which i can’t even fly

When using BeyondATC, I get a taxi clearance (from gate 61L to rwy 04) via taxiway H with a lot of other - incorrect - designators (P, N and L). At least in the case of ‘P’, I can confirm this using Little Nav Map: A very short section of taxiway H is labelled P and BeyondATC is picking that up. I suppose that this is also the case for the other designators. Could you please verify this?

Greetings! I am happy to report that update v1.0.10 fixed - at least for me - all of the problems with the GE variant I had posted about. I installed the update and then loaded the aircraft. Everything was as it should be. I will take it on a flight this evening. Thanks to everyone who helped with this! Regards, Scott

Hello, is there any update to this? It's a 10 minute fix with a 30 min push to servers, yet here we are, 2 months later and still no fix....

Hello iniBuilds team, I am a regular customer on the iniStore (I own several of your sceneries). I wanted to share some feedback on the F406 Caravan II after testing it, including the latest update. 1. Floodlight not working The floodlight (the main overhead light in the cabin) does not seem to function at all. There is no switch or control that turns it on or off. This is quite disappointing because the aircraft manual clearly mentions a floodlight, and even older add-ons like the Titan 404 have a working one. At night, this really hurts immersion and makes the cabin almost unusable in dark conditions. 2. Propeller levers too sensitive The propeller levers are extremely sensitive in the upper part of their range. Even when using the mouse for precise control, small movements cause very large changes in RPM. This makes fine adjustments difficult, especially during cruise or when trying to set precise power settings. 3. Overall systems depth (especially engine) I also own the 414, 850 and M500. Compared to these, the systems depth on the F406 feels noticeably lighter. In particular, the engine simulation (ITT behavior during start and in flight) seems quite simplified and forgiving. It doesn’t deliver the same level of realism I was hoping for on a twin PT6 aircraft. The aircraft looks good visually and has nice mission features, but on the technical side (lighting, prop control feel, and engine thermodynamics) it currently feels unfinished or lacking compared to what one would expect at this price point. I’m posting this in the hope that these points can be looked at in a future update. If the team needs more details, screenshots, or specific conditions where the issues appear, I’m happy to provide them. Thank you for your work on the F406.

Yeah cant click anything on the overheard.. takes forever to find the super small clickspot for the button. Unflyable :( Never had this issue with another aircraft. Only the ini a300

I don't know how this passed testing, but on the current patch, the L1011 wildly changes the EPR on TM/VNAV climb and the aircraft will literally go into a 1000ft or greater descent during VNAV climb to catch the speed it's trying to climb at. Not only that, once the aircraft is level in cruise, it descends AND climbs anywhere from 500 to 1000 feet as it tries to maintain speed (I guess??). It literally cannot maintain level flight. Guys, this is bad. The TM mode is completely unusable.

I’ve also noticed that EFOB at destination increases as the CI is increased. Flight time does reduce, but so does the fuel usage, which is not the way it should be.

Same. It's been like this since the beginning. Incredible that no one picked up on this sooner.

Thanks Mike. Much appreciated. I trust this is for the -500 version.

Yep, I too have this same issue. Very frustrating, and therefore now unflyable. Keith

I made a forum post on this last year and it was already fixed. It is correct to the a340's synthetic voice style. 1. Why are we using AI... 2. It is already fixed, it isn't like the RA callouts that were originally in the aircraft that were ripped from the a350/ airbus gpws callouts off of youtube

Hi There, Its been a month.

Since aerosoft and LVFR has implemented taxi camera on their aircraft using different approaches, is inibuilds trying any workaround to implement taxi cameras as well?

I'll pass this along to the team, thank you.

Here is some data for you

I am seeing the exact same behavior in the exact same way.

Hi everyone, this is not new but I've never seen anyone mention it. This is probably very specific to the D-AEAF DHL livery but may be present on other liveries aswell whenever they have sprites around this area. Whenever the door controls hatch door next to the main cargo door is opened, the red sprite above the door doesn't animate, but there is some weird shading going on instead. Nothing too bad but maybe worth checking at some point. Cheers!

Hi everyone, first of all thanks for the latest update. The long term support for your first aircraft is much appreciated and for me it gets more perfect and fun to fly with every update! With 1.0.10 I've noticed some strange behaviour of the APU heatblur. It appears to remain in place where it was rendered for the first time, not moving with the aicraft at all. At the arrival airport there is no heatblur at all becaus I guess it still animates at the departure stand. 😄 I'm not using any effect mods, this is pretty much a vanilla install. Maybe you can take a look when time allows? Thank you!

I've passed this along to the team, thank you :)

Hello, at this point in time we recognize the advances that Xbox has made but due to performance reasons are still not able to implement the above items on to the Xbox platform, Thank you for understanding as well as the compliments for the team :)

Fixed in 1.0.10. Can be marked as solved, thank you very much!