ekosif

Hello, Thanks for reply. I could make only 2 flights with 1.0.10 and didn't have this issue, it was not happening every time with the 1.0.9 as well so I am not sure it is fixed with new version or I didn't meet it with it yet. I will check the Discord channel, thanks for suggestion.

I know a few of the items are already solved with 1.0.10 but what about the others, is there any plan for it? @iniBuilds

Hello, I could fina lly hear the cabin announcement first time since the product is released but I suppose there is something wrong with it. In order to hear it from the cockpit, I have to keep transmit button selected for the CAB even though receive is already selected. If I do this I can clearly hear the announcements but this time I have to select VHF1 transmit every time in order to talk with others/ATC. And also, I got cabin is ready for landing announcement just after take off 🙂

Also same, even button click sound is delayed.

Will any person from inibuilds have a look at this or should we just ignore it?

If you wait enough than they should start automatically after completing the cooling phase. Did you wait to reduce the egt or abort the start up?

It happened to me even with the updated navdata, so I don't think it is related with it(I tried two different navdata). I tried KJFK-EHAM which are very old airports so even without updated data, those airports must still be there, I don't think we can go back that much. After I got this issue, I restarted the flight from same airport again, issue was still there. And then I made a flight from LTFM to WSSM without any issue.

Hello, I would like to summarize a few bugs with 1.0.9. I have prepared a flight from New York (KJFK) to Amsterdam (EHAM). I have updated navigraph cycle. But with two different try, I got AIRPORT NOT IN DATABASE error when I tried to import the flight plan. I also tried to enter them manually but neither KJFK nor EHAM could be entered to the MCDU. I got config pitch trim not in T.O Range warning, screenshot attached. As can be seen, it is adjusted very well as per the reference, I also tried to change it manually but no chance. Also before get this error, T.O Config item for take off checklist cannot be turned to green, it stayed blue. (Not happened on first flight, got it on second flight but it was another day, not turnaround) After take off, I got a warning and ECAM action regarding to CG (ZFWCG was entered correctly and double checked with OIS data). Most probably this is related with the item 2. It calculates different values from what it shows. Cabin announcements still cannot be heard from cockpit. Autobrake Off callout is still missing. Still no clunk sound while switching between Ground power and APU and vice versa. Still no clunk sound when engine is turned off. Still no auto ANF activation on touch down. I don't really mind this one but during cold and start operation, EGT1 shows >300 degC where EGT2 is around 10. Therefore have to wait for cooling during start up. No send button for PDC. Request can be transferred to mailbox but there is no send button therefore had to cancel it. Improvements Thanks for improving the EGT behaviour during engine start up, it was annoying to see the temp jump just before engines become available. Sounds are much better, especially during taxi. But one weird noise during deceleration, during the approach and deceleration, noise level increases very quickly when the speed is approaching to ~250 knots. Performance is better comparing with 1.0.8. Handling the aircraft is very good - I am not mentioning about realism here as I am not real pilot but it is more fun in the sim like this in my opinion. Thanks for adding the route to the enroute map.

Sorry to hear that, I hope they release a fix soon. And unfortunately uninstalling and installing the sim itself is not easy task allways because of lots of addons and settings.

Thanks for your message. I am not using framegen, its not natively supported with my card as I have 3080 ( I know some mods but never tried them). For the lossless scaling, I have it but it was not active as I had good fps when its frozen, rarely using it on the ground to be honest.

Hello, Together with my previous bug reports for 1.0.8, I have another really annoying and frustrating bug with A350. I am making flights almost every night and generally I am trying to fly with A350 as I like that bird. But here after sitting 6 hours and 20 min flight from KJFK to EHAM, simulator is frozen! This is third time happening with A350 (not the same route, completely different routes), waste of almost 20 hours, not with any other aircraft. I can hear the sounds, I hear the warning sounds when I disconnected autopilot for example, plane is moving, when I press the ESC button aircraft sounds go away and I can hear the menu item sounds when I hoover my mouse but screen is completely frozen in the cockpit. I am not able to report wasm faults as no movement on the simulator, but again it is working normal in the background. It really pissed me off. As I am flying with virtual airline, autosave function is not recovering my task. I just want to go back to 1.0.7 since everything was fine there even with better fps! Again, this is not happening with any other aircraft so I don't think something is wrong with the simulator itself. I don't know what to do tbh..

I checked again and it seems turbulance settings is not affecting it at all. It starts slowly the moment I clicked to 4x and than becoming very serious movements in just 2 or 3 seconds. I really, really enjoy with this aircraft, hope all the issues are solved very soon and start flying with it again.

Hello, I will check and get back to you when I get in the sim again but nothing has changed in terms of sim settings between 1.0.7 and 1.0.8. All the settings are completely identical.

Hello, I would like to summarize a few issues here with 1.0.8: 4x time compression is not usable: I have explained in another topic but to mention also here, when I enabled the time compression with 4x, aircraft rolling continuosly left and right very hard, above 50% bank angle.. I am not even able to click disable button for the time compression on OIS becuase of very harsh movement of the aircraft. I had to use active pause function to disable it. (FL410 with very calm and stable wind) ANF is not activated automatically after touched down. No autobrake off callout (BTV was set and disabled around 60 knots) After arrived to gate and shut the engines down, there are literally no clunk sound and flashing the cockpit lights. I had to check ECAM again to ensure engines are off.. Even GSX didn't realize they are off. But N1 and N2 were 0, no fuel flow, EGT was still around 360 degC after 15 seconds. Also no clunk sound and flashing after activating the GPU and shutting the APU. It felt like I deboarded and secured the aircraft while engines are still running. Performance decreased after update. Previous versions were generally better. It was very hard to click the MCDU and OIS, they didn't sense anything unless zoom in to screens. That was not the case with previous versions. Finally I got the cabin announcements with 1.0.7 but it is gone again with this update. I am not sure if it is bug but after landing gears down during approach, I saw that brake pressures were increasing and decreasing, couldn't understand the reason and didn't notice before. As an imprevement, cockpit sounds during taxi was much better than previous versions. But generally I regret every bit of this update unfortunately. I hope inibuilds goes back to weekly updates again for some time to address the issues as before.. PS: I cleared the WASM folder before update. Anyone please let me know if you also have these issues.

Hello, After 1.0.8 update, auto time compression is not usable at 4x. Everything is OK with 2x but the moment I switch to 4x aircraft starts rolling left and right really hard, I am not even able to disable time compression because of the movement (FL410 with very stable and calm wind). I had to pause the simulator from top menu and then recovered it. Tried many many times, every time it is doing this behavior. It was working very well on previous versions but not with 1.0.8 and it is making really hard the long haul operations