February 2, 20242 yr 8 minutes ago, btacon said: Do you own the Fenix? Yes I do. What's your point? Since there is no any expectations to get Fifi's Blok 2 in the next six months we have time to talk about something else. P.S. Why "Fifi"? I like the word but what is behind it?
February 2, 20242 yr Just now, G-YMML1 said: Nope. IAE model still hasn't been released more than 12 months after release of CFM model. Because people complained that the CFM fuel burn was off. So to fix that, they went with the external engine model for the IAEs, realised the updated CFM external engine model was nearly complete also. However, Fenix came a cropper with some "roadblocks" in their own coding and due to some issues created by Asobo. AMD Ryzen 5800X3D; MSI RTX 3080 Ti ; 32GB Corsair 3200 MHz; ASUS VG35VQ 35" (3440 x 1440) Fulcrum One yoke; Thrustmaster TCA Captain Pack Airbus edition; MFG Crosswind rudder pedals; miniCockpit FCU; CPFlight MCP 737; Logitech FIP x3; TrackIR MSFS; Fenix A320; A2A PA-24; HPG H145; PMDG 737-600; AIG; RealTraffic; PSXTraffic; FSiPanel; REX AccuSeason Adv; FSDT GSX Pro; FS2Crew RAAS Pro; FS-ATC Chatter
February 2, 20242 yr Just now, G-YMML1 said: Nope. IAE model still hasn't been released more than 12 months after release of CFM model. Maybe I missed something in your post. You weren't talking about the dev time, you seemed to be talking about their packaging of the models. Did I miss something? The delay for IAEs has been well explained by FNX. If you're talking about why didn't they just do all the variants in the first release, not really sure. Probably because all that takes time in the way they are simulating the aircraft. Kinda makes sense, but with the hit they took on the visual model, it appears to have taken much longer than they wanted. Jeff D. Nielsen (KMCI) https://www.twitch.tv/pilotskcx https://discord.io/MaxDutyDay VENGEANCE a8200 Gaming PC: AMD Ryzen 9 9950X3D, GeForce RTX 5080, 64GB DDR5, 4TB (2TB/2TB) M.2 SSD, Win11 Pro
February 2, 20242 yr 2 minutes ago, Vitold69 said: Yes I do. What's your point? Since there is no any expectations to get Fifi's Blok 2 in the next six months we have time to talk about something else. P.S. Why "Fifi"? I like the word but what is behind it? I’m trying to figure out your point. You’re the one making all the claims, what’s your point other than to spread shade all over Fenix?
February 2, 20242 yr Just now, F737MAX said: Because people complained that the CFM fuel burn was off. So to fix that, they went with the external engine model for the IAEs, realised the updated CFM external engine model was nearly complete also. However, Fenix came a cropper with some "roadblocks" in their own coding and due to some issues created by Asobo. Is it sarcasm or what? Sorry, English is not my native language. 9950X3D, X870E ROG CROSSHAIR HERO, Corsair Dominator Titanium 64GB DDR5-6000 PC5-48000, ASUS RTX 5070Ti 16GB, 9100 PRO 4TB Samsung ,990 PRO 4TB Samsung, AX1600i 1600 Watt 80 Plus Titanium ATX, ASUS 360 ARGB EXTREME 360mm Liquid CPU Cooling Kit.
February 2, 20242 yr 14 minutes ago, G-YMML1 said: Nope. IAE model still hasn't been released more than 12 months after release of CFM model. Neither was FSLabs done in a year.
February 2, 20242 yr Just now, carlanthony24 said: Neither was FSLabs done in a year. At least they tend to release each line (320 first - then 321 and 319) with both engine types simultaneously, Ok, if incorrect fuel flow requires Fenix to rework everything, then perhaps my concerns and questions here are pointless. It's a different level of development nirvana, which I'm not familiar with, so I'm out of this topic for now 🙂 9950X3D, X870E ROG CROSSHAIR HERO, Corsair Dominator Titanium 64GB DDR5-6000 PC5-48000, ASUS RTX 5070Ti 16GB, 9100 PRO 4TB Samsung ,990 PRO 4TB Samsung, AX1600i 1600 Watt 80 Plus Titanium ATX, ASUS 360 ARGB EXTREME 360mm Liquid CPU Cooling Kit.
February 2, 20242 yr Just now, G-YMML1 said: Is it sarcasm or what? Sorry, English is not my native language. No sarcasm. By using MSFS flight modelling parameters, the Fenix CFM fuel burn is (IIRC) about 5% off from the real world data. To fix that, Fenix decided to go down the route of externally modelling the engines. With Fenix's emphasis on getting small details right, their initial focus was on one engine variant before the other. Should they have taken longer to get both engine variants out at initial release? That's a commercial decision that only they can answer. People can say 'feature creep', Aamir being too picky, poor project management, poor marketing/customer relations. And they could have a strong case. But software development is not a linear progession and the Fenix team is trying to bring new levels of detail to home flight simulation. Issues will occur, especially with MSFS being a moving target, rather than the relatively static platforms flight simmers were used to before MSFS2020 arrived. AMD Ryzen 5800X3D; MSI RTX 3080 Ti ; 32GB Corsair 3200 MHz; ASUS VG35VQ 35" (3440 x 1440) Fulcrum One yoke; Thrustmaster TCA Captain Pack Airbus edition; MFG Crosswind rudder pedals; miniCockpit FCU; CPFlight MCP 737; Logitech FIP x3; TrackIR MSFS; Fenix A320; A2A PA-24; HPG H145; PMDG 737-600; AIG; RealTraffic; PSXTraffic; FSiPanel; REX AccuSeason Adv; FSDT GSX Pro; FS2Crew RAAS Pro; FS-ATC Chatter
February 2, 20242 yr Just now, G-YMML1 said: At least they tend to release each line (320 first - then 321 and 319) with both engine types simultaneously, Ok, if incorrect fuel flow requires Fenix to rework everything, then perhaps my concerns and questions here are pointless. It's a different level of development nirvana, which I'm not familiar with, so I'm out of this topic for now 🙂 So that is up to them. Developers can do what they want. Fenix are choosing to fix the issues first than release anything further. You have to remember Fenix got code from ProSim then removed that code and built code from scratch. When you and other see the change log then hopefully you all understand.
February 2, 20242 yr 3 minutes ago, carlanthony24 said: So that is up to them. Developers can do what they want. Fenix are choosing to fix the issues first than release anything further. You have to remember Fenix got code from ProSim then removed that code and built code from scratch. When you and other see the change log then hopefully you all understand. The issues were actually fixed a long time ago according to Amir, it was the visual model which cost them the time. ASOBO, IRRC, had not documented things correctly or were missing things all together. That's what caused FBW to plan to do a complete re-work (prior to deciding to concentrate on the 380) of the 320 model itself (blender tools missing?). Edited February 2, 20242 yr by Jeff Nielsen Jeff D. Nielsen (KMCI) https://www.twitch.tv/pilotskcx https://discord.io/MaxDutyDay VENGEANCE a8200 Gaming PC: AMD Ryzen 9 9950X3D, GeForce RTX 5080, 64GB DDR5, 4TB (2TB/2TB) M.2 SSD, Win11 Pro
February 2, 20242 yr Just now, Jeff Nielsen said: The issues were actually fixed a long time ago according to Amir, it was the visual model which cost them the time. ASOBO, IRRC, had not documented things correctly or were missing things a together. That's what caused FBW to plan to do a complete re-work (prior to deciding to concentrate on the 380) of the 320 model itself (blender tools missing?). Yeah but then broke hence Fix the issues. External engine model I doubt was complete a long time ago.
February 2, 20242 yr 5 minutes ago, carlanthony24 said: Yeah but then broke hence Fix the issues. External engine model I doubt was complete a long time ago. What broke was the visual model, not the engine model as far as I can remember. Maybe I'm wrong. I thought Amir said it was something about the mapping they had to re-do. When you say issues (bugs and what not), are 2 different things in my eyes. The engine model was planned to be external from the start, I thought. Edited February 2, 20242 yr by Jeff Nielsen Jeff D. Nielsen (KMCI) https://www.twitch.tv/pilotskcx https://discord.io/MaxDutyDay VENGEANCE a8200 Gaming PC: AMD Ryzen 9 9950X3D, GeForce RTX 5080, 64GB DDR5, 4TB (2TB/2TB) M.2 SSD, Win11 Pro
February 2, 20242 yr 13 minutes ago, F737MAX said: No sarcasm. By using MSFS flight modelling parameters, the Fenix CFM fuel burn is (IIRC) about 5% off from the real world data. To fix that, Fenix decided to go down the route of externally modelling the engines. With Fenix's emphasis on getting small details right, their initial focus was on one engine variant before the other. Should they have taken longer to get both engine variants out at initial release? That's a commercial decision that only they can answer. People can say 'feature creep', Aamir being too picky, poor project management, poor marketing/customer relations. And they could have a strong case. But software development is not a linear progession and the Fenix team is trying to bring new levels of detail to home flight simulation. Issues will occur, especially with MSFS being a moving target, rather than the relatively static platforms flight simmers were used to before MSFS2020 arrived. It's Amir being too picky...lol. That's a good thing, IMO. I don't their marketing or customer relations was anywhere close to being poor. Things just didn't work out on the timeline they wanted it to. Stuff happens. It's not anywhere near the big deal some people are making it out to be. Jeff D. Nielsen (KMCI) https://www.twitch.tv/pilotskcx https://discord.io/MaxDutyDay VENGEANCE a8200 Gaming PC: AMD Ryzen 9 9950X3D, GeForce RTX 5080, 64GB DDR5, 4TB (2TB/2TB) M.2 SSD, Win11 Pro
February 2, 20242 yr 11 minutes ago, Jeff Nielsen said: What broke was the visual model, not the engine model as far as I can remember. Maybe I'm wrong. I thought Amir said it was something about the mapping they had to re-do. When you say issues (bugs and what not), are 2 different things in my eyes. The engine model was planned to be external from the start, I thought. yeah the visual model is what broke with what ever else was broken before that, but people above saying about external engine model.
February 2, 20242 yr 1 hour ago, Vitold69 said: It’s so interesting to see how many users who paid for the product justify by all means the endless delay. They already produced an already excellent (with multiple updates) A320 which cost me under 50 quid. If they went bust tomorrow I would still feel happy with my purchase. FSlabs took a few ice ages to get their updates out of the door. Why the Fenix hate? Do we just hate on developers as a matter of course in this hobby now? Specs: 11900K (5ghz), 64GB ram 3600mhz, RTX 3080 ti
Archived
This topic is now archived and is closed to further replies.