ekosif

That is the most nonsense comment I have ever read here in forum, even frank couldn't reach that level, so congratulations! You don't have to read all the topics, if you are tired, be proactive and look somewhere else, no one is expecting anything from you.

I only use Vatsim, GSX and airports that I take off and land, what are the suspicious add-ons? I don't think these addons will cause any problems as they are widely common. And also, since this is the forum of the iniBuilds, I don't think there is anything wrong to report the problems here. Otherwise why would you have a special section for it, right? I am not sure what made you chuckle but really sick of the people like above who jumps between the topics and acts like forum moderator. We are having unique problems and we will report them to let you know and hope for the solution.

Just ignore that character, waste of time.

Thanks for the answer. It was two different route with same livery, Istanbul to Berlin and Berlin to Stockholm Arlanda. This is the route for last flight: EDDB/24R BIKPO1A BIKPO Y89 RENKI L132 DEMUR N746 GORPI DCT ARMOD Z228 NILUG NILUG2J ESSA/01L

I am not the person who seeks after impressions, like you. I know which section I am looking at as I use both sims but obviously that system is common so the bugs. But of course you have to confirm it before other forum users tag it as bugs. Another speech from self promoted forum admin. Next time we all will ask you if it is a bug or we need to create a new topic. Don't worry.

You have serious problems with interfering others business, and I suppose also capability of understanding what you read. No one asked you for your opinion, buddy. I asked ini teams, they may confirm it or suggest something else, either way OK for me. I am not sure if you are trying to chase career in ini teams or being here to annoy others with your personality, but get the hell out of here and mind your own business. PS: Look at the other forum users, if they have the same issue, they just contribute. If they have the solution or work around, they share to help others. And look at your own attitude (or ask help from someone else to criticise it for you) Again, no one asked your opinion. I will copy and paste the same message below again, for obvious reasons. You have serious problems with interfering others business, and I suppose also capability of understanding what you read. No one asked you for your opinion, buddy. I asked ini teams, they may confirm it or suggest something else, either way OK for me. I am not sure if you are trying to chase career in ini teams or being here to annoy others with your personality, but get the hell out of here and mind your own business. PS: Look at the other forum users, if they have the same issue, they just contribute. If they have the solution or work around, they share to help others. And look at your own attitude (or ask help from someone else to criticise it for you) Again, no one asked your opinion.

Hi, @iniSteven, @LineDX, Thanks for the response. I will try to replicate it on the next flight. @LineDX, problem is not about climb performance, aircraft levels off at random altitude and N1 decreases accordingly. When I push the knob N1 increases again and start climbing. Similar things happen for descend as well but vice versa for the N1 levels. The thing is, I am having this issue and VNAV issue with Lufthansa livery, didn't have this behavior with Turkish, Etihad or Qatar. Not sure if there is any relation between them.

You are NOT the person who will confirm it, got it? I've tried to explain it to you politely but obviously there is something you are not able to understand, this is not your responsibility so just mind your own business and let the rest to ini team. If you are having same issue then add your experience. If you have solution, share it with others. Otherwise just read and keep surfing. Don't create unnecessary crowds here. Yes, I didn't develop just one line of code in my 13 years of work experience. Maybe you teach me some coding and error management. Obviously you have knowledge about everything. If anyone from ini team reads this, give this guy a role so he/she can formally approve or disprove the bugs on behalf of you.

Hey @frank_m, look another topic for TCAS, for the same issue! Let's bring your expertise here and ask also them what they want/expect..

OK, I don't understand why you are trying to argue with me but let me make one thing very clear for you; you are just blog member and you are not in a position that you can say it is definetely not bug or it is bug, you can advise if you have anything to help to others. You don't have the details neither their backends nor details of my case so do not make judgement by yourself on behalf of others. Every bug is reported by one person first and then others join it. This can be route specific, livery specific or variant specific and others may not make any flight with that combination. As an old habit, I never update two system at the same time to make the debugging easier. So in this case, I only updated A350 without any other update like scenery, addon or something. I exclude Navigraph for that one beucase it is generally very straight forward. On the other hand, after that flight, I made another flight with same route and same addons with Fenix320, without any issue. ( I am not even saying I didn't have that problem before I updated the A350 ) I already answered this, so just paste the previous answer: So, as a customer, and let's assume he/she just wants to make a flight without any system knowledge, if all other aircrafts are working OK but this one not then you would chase for the problems for that particular addon, right? (It was a statement, not a question, just in case 😉 )

I am NOT mentioning about the past statements here, that's not even a valid viewpoint, of course they might mention about the TCAS a few months ago but hey look, still having problem here? Regarding my VNAV problem, my navdata is correct and up to date. No problem with PMDG products or Fenix 320 or ini 330, so this one is the only problematic one. Therefore you can not blame the navdata. Flightplan is standart Simbrief flightplan and I've never see any single person had conflict in that. And I clearly indicated above that there were no waypoints for next 50 miles (no direct to as well). You said a lot of people would complain, but here is the one item from last update: Fixed - WASM texture loading bug introduced in SU4 on some machines As you can see, some bugs do not occur on every user. I don't know how you can say this is DEFINETELY not a bug but let me say it very clearly, I don't think you are the person who decides it is bug or not. Let me summarize it for you again, if your simulator and all other systems and addons work without any issue with the other aircrafts but not with the A350 then you can consider it as a product bug. I am a SW engineer with master degree, if your SW is not working on all of your target systems or platforms then you are doing something wrong on fail catching or management and you are not robust against different noise factors and that is also a BUG!

Hello all! Tbh, I am really pissed off. Each update fixes something but break another thing. Now one of the essential feature is not working properly, which is VNAV!. Last time I've reported incorrect TCAS callouts but no one from ini team had a look at it. Now I am in trouble with VNAV (not happened just one time!). During the climb, aircraft stop climbing at random altitude even though there is no restriction or mode/target altitude change. For example, I set climb to FL240 with managed mode, but it stop climbing at FL120, then I push the altitude button, it continue to climb but stops again at FL175... So in order to reach desired altitude, I have to push the altitude knob several times, which is really annoying after some time! During descend, same thing also happens. I have to push altitude knob several times to descend to desired altitude. Again, no restriction or change on anything! There was not even any point in front of me for next 50 miles! And also, during approach with ILS, it randomly switches from G/S mode to vertical speed mode, literally for no earthly reason! A considerable amount of time has passed since the plane was released but we are still struggling with basic and essential bugs. I personally don't have unlimited time so trying to make a flight in very limited time window and do not want to spend my time with this kind of things.

And it is still not aligned so you are not able to see the bottom part of the HUD, and this is the case since first release. Also, with latest update, it seems normal mode and cross wind mode switched. It was vice versa before 1.1.9 update.

Hello! I got very weird TCAS advisory during cruise. As can be seen from the screenshot below, I got TCAS alert even though there is 6500 feet between me and other aircraft, and there is no possible conflict as both aircraft were heading almost opposite sides. And this was not the only one I got, I almost got TCAS alert every traffic flew under me, some of them were not even visible in the MFD due to huge altitude difference. Also those green/red bars in the PFD was there for entire flight even after clear of conflict callout.

Hi @Eddie, Nothing has changed for the HUD with new update. It is still not aligned correctly and also bird is not still visible during approach if there is cross wind.