- UID
- 118169
- 注册时间
- 2021-9-30
- 在线时间
- 小时
- 最后登录
- 1970-1-1
- 精华
- 阅读权限
- 50
- 听众
- 收听
已绑定手机
|
- [backcolor=var(--background-mentioned)][color=var(--text-normal)]Hey [color=var(--brand-experiment-200)]@everyone. I hope I'm not jinxing anything, but I believe we may have just built our final release candidate - which means it's time to talk about a few things and I'm sorry but this'll be a long one!Lets start by getting this out the way: release schedule. We're going to let this RC build sail the high seas of our notoriously meddlesome testers for a little while, just to be confident we're not about to ruin a few thousand people's day. We expect this process to take a day or two depending on what shows up. As much as I'd love to hold onto our little A320 until every single aspect is perfect in our eyes, the reality is you have to draw a line under it at some point and throw it out of the nest. This has been an absolute labour of love, all-nighters and passion to create a flight simulation experience we want - and hopefully you do too.This being our first product launch, and not one that looks likely to fly under the radar if we make a mess of it, we're doing our best to prepare all aspects of the product purchase/install/user experience etc. We WILL invariably get something wrong - hopefully small, but just know we're putting our all into this and anything that comes up will be resolved as quickly as possible. With that said, if potential day 1 issues are not your jam by all means steer clear for a while - there are no badges handed out for purchasing the moment it's available; we'd rather every customer was a happy one. Sit back, watch some videos, read the reviews from those you trust, see whether it's right for your simming needs (I know some of our devs spend far too long in the BAe 146...).I'm going to do something a bit unusual here and talk about some of the weaknesses of our unreleased product. Stuff I would want to know before purchasing. There's two big ones I'd like to address: engines and DUs. Engines are a fun one, MSFS gives us a single point of tuning for fuel-flow - either it puts out some Saturn V flow figures in climb at low altitude, or it sips fuel in the cruise - there's just no winning. We've fretted over it as best we can, and we're seeing about a 6% margin to the real numbers, balancing all aspects of flight and then rounding up on the slightly more efficient side so you land with a few gallons more than you need, not a few less...! Ultimately we think the best way forward is a fully custom engine model. We actually already started poking in this route with start-up/shut-down, EGT, spool times etc - but to go much further and do it properly requires some SERIOUS work, and might not prove fruitful for some time. Given we're so close to the numbers already, holding back for an undefined period of time (at least a few months) doesn't seem worth it. Quite frankly, to the average eye nothing will appear amiss, but you guys are far from average aren't you? Once post-launch clean-up calms down, we'll get cracking on a fully 'Fenix' engine solution. We'll also take a closer look at the displays. We're not entirely happy with them either, despite how minor and cosmetic the issues are (shape scaling, text positioning etc). But again, we want to tackle it properly rather than with ducktape and prayers. If you're not really sure what I'm talking about at this point on either of these items, it gives you an idea of how relatively minor they are in the scale of things. But transparency counts for a lot in this community, so I'd rather talk about it at the risk of scaring some people than ignore it.Not only will we be working on the aforementioned, but hundreds of other bits that caught our eye during development that couldn't be justified within the product scope...at that time. For us, the excitement of release is closing this chapter of development, and starting a whole new one. Everyday the list of "OOOOH LETS DO THIS" grows. Anyway, less talk more show on that front, we're excited.
[backcolor=var(--background-primary)][color=var(--interactive-normal)]
- [backcolor=var(--background-message-hover)]
[color=var(--text-muted)][size=0.6875][08:44] [color=var(--text-normal)]Now there's been lots of talk about how we run our systems external to the sim, which we do, however we also use the same system as FSUIPC and Aerosoft's VGDS to automatically handle that side of things for you. Provided MSFS runs exe.xml (which it has been struggling to do on occasion since SU9 - Asobo are aware but we're not holding release when it's working for the majority) you can simply load MSFS and select our A320 like any other, go fly and apart from a moment after load where the internal and external systems perform a momentary handshake, it's like any other aircraft. If MSFS decides not to use it's own exe.xml, just open the Fenix App at any point before or after loading the sim and it'll handle the rest - nothing else required. The advantages to this method are plenty, such as allowing you to select which piece of hardware to render the displays on to ease a performance bottleneck specific to the system it's running on. We don't deal with serial numbers, 2FA, emails with verification links etc: just download the installer and login with your account details you used to purchase the product. So long as you don't completely uninstall Fenix, you shouldn't be prompted to login or do anything else outside MSFS again. There's two things to keep in mind about this system: 1. it requires an internet connection on login, but will happily function offline as long as the Fenix App is open. 2. To keep it this simple, we do tie each license to one machine at this time, but as soon as our colleagues in Ukraine are back up and running we'll be expanding this out to 3 machines and generally improving the process. For what it's worth, you can swap install PCs as many times as you like, just ping support and they'll reset Hey @everyone. I hope I'm not jinxing anything, but I believe we may have just built our final release candidate - which means it's time to talk about a few things and I'm sorry but this'll be a long one!Lets start by getting this out the way: release schedule. We're going to let this RC build sail the high seas of our notoriously meddlesome testers for a little while, just to be confident we're not about to ruin a few thousand people's day. We expect this process to take a day or two depending on what shows up. As much as I'd love to hold onto our little A320 until every single aspect is perfect in our eyes, the reality is you have to draw a line under it at some point and throw it out of the nest. This has been an absolute labour of love, all-nighters and passion to create a flight simulation experience we want - and hopefully you do too.This being our first product launch, and not one that looks likely to fly under the radar if we make a mess of it, we're doing our best to prepare all aspects of the product purchase/install/user experience etc. We WILL invariably get something wrong - hopefully small, but just know we're putting our all into this and anything that comes up will be resolved as quickly as possible. With that said, if potential day 1 issues are not your jam by all means steer clear for a while - there are no badges handed out for purchasing the moment it's available; we'd rather every customer was a happy one. Sit back, watch some videos, read the reviews from those you trust, see whether it's right for your simming needs (I know some of our devs spend far too long in the BAe 146...).I'm going to do something a bit unusual here and talk about some of the weaknesses of our unreleased product. Stuff I would want to know before purchasing. There's two big ones I'd like to address: engines and DUs. Engines are a fun one, MSFS gives us a single point of tuning for fuel-flow - either it puts out some Saturn V flow figures in climb at low altitude, or it sips fuel in the cruise - there's just no winning. We've fretted over it as best we can, and we're seeing about a 6% margin to the real numbers, balancing all aspects of flight and then rounding up on the slightly more efficient side so you land with a few gallons more than you need, not a few less...! Ultimately we think the best way forward is a fully custom engine model. We actually already started poking in this route with start-up/shut-down, EGT, spool times etc - but to go much further and do it properly requires some SERIOUS work, and might not prove fruitful for some time. Given we're so close to the numbers already, holding back for an undefined period of time (at least a few months) doesn't seem worth it. Quite frankly, to the average eye nothing will appear amiss, but you guys are far from average aren't you? Once post-launch clean-up calms down, we'll get cracking on a fully 'Fenix' engine solution. We'll also take a closer look at the displays. We're not entirely happy with them either, despite how minor and cosmetic the issues are (shape scaling, text positioning etc). But again, we want to tackle it properly rather than with ducktape and prayers. If you're not really sure what I'm talking about at this point on either of these items, it gives you an idea of how relatively minor they are in the scale of things. But transparency counts for a lot in this community, so I'd rather talk about it at the risk of scaring some people than ignore it.Not only will we be working on the aforementioned, but hundreds of other bits that caught our eye during development that couldn't be justified within the product scope...at that time. For us, the excitement of release is closing this chapter of development, and starting a whole new one. Everyday the list of "OOOOH LETS DO THIS" grows. Anyway, less talk more show on that front, we're excited.Now there's been lots of talk about how we run our systems external to the sim, which we do, however we also use the same system as FSUIPC and Aerosoft's VGDS to automatically handle that side of things for you. Provided MSFS runs exe.xml (which it has been struggling to do on occasion since SU9 - Asobo are aware but we're not holding release when it's working for the majority) you can simply load MSFS and select our A320 like any other, go fly and apart from a moment after load where the internal and external systems perform a momentary handshake, it's like any other aircraft. If MSFS decides not to use it's own exe.xml, just open the Fenix App at any point before or after loading the sim and it'll handle the rest - nothing else required. The advantages to this method are plenty, such as allowing you to select which piece of hardware to render the displays on to ease a performance bottleneck specific to the system it's running on. We don't deal with serial numbers, 2FA, emails with verification links etc: just download the installer and login with your account details you used to purchase the product. So long as you don't completely uninstall Fenix, you shouldn't be prompted to login or do anything else outside MSFS again. There's two things to keep in mind about this system: 1. it requires an internet connection on login, but will happily function offline as long as the Fenix App is open. 2. To keep it this simple, we do tie each license to one machine at this time, but as soon as our colleagues in Ukraine are back up and running we'll be expanding this out to 3 machines and generally improving the process. For what it's worth, you can swap install PCs as many times as you like, just ping support and they'll reset it immediately, no questions asked.Lastly, we'll try to give as much warning as we can when we have a release date & time. We're feeling confident about our infrastructure but I'm not promising any steak dinners.-Aamirit immediately, no questions asked.Lastly, we'll try to give as much warning as we can when we have a release date & time. We're feeling confident about our infrastructure but I'm not promising any steak dinners.-Aamir
- 嘿大家。我希望我没有搞砸任何事情,但我相信我们可能刚刚构建了我们的最终候选版本——这意味着是时候谈谈一些事情了,很抱歉,这会是一个很长的话题!让我们从解决这个问题开始:发布时间表。我们将让这个 RC 建造在我们臭名昭著的爱管闲事的测试人员的公海中航行一段时间,只是为了确信我们不会毁掉几千人的一天。我们预计这个过程需要一两天的时间,具体取决于显示的内容。尽管我很想抓住我们的小 A320,直到每一个方面在我们眼中都是完美的,但现实是你必须在某个时候在它下面画一条线,然后把它扔出巢穴。这绝对是爱、通宵达旦和激情创造我们想要的飞行模拟体验的劳动——希望你也这样做。这是我们的第一个产品发布,如果我们把它弄得一团糟,它看起来不会被忽视,我们正在尽最大努力准备产品购买/安装/用户体验等的各个方面。我们将始终如一出了点问题——希望很小,但只要知道我们正在全力以赴,任何出现的问题都会尽快得到解决。话虽如此,如果潜在的第 1 天问题不是您的问题,请务必暂时避开 - 没有任何徽章可供购买;我们宁愿每个客户都是快乐的。坐下来,观看一些视频,阅读您信任的人的评论,看看它是否适合您的模拟需求(我知道我们的一些开发人员在 BAe 146 上花费的时间太长了......)。我将在这里做一些不寻常的事情,并谈谈我们未发布产品的一些弱点。购买前我想知道的东西。我想解决两个大问题:引擎和 DU。发动机很有趣,MSFS 为我们提供了燃油流量的单点调整——要么在低空爬升时输出一些土星 V 流量数据,要么在巡航时吸油——没有胜利。我们已经尽最大努力对此感到担忧,我们看到实际数字大约有 6% 的余量,平衡了飞行的各个方面,然后在效率稍高的一侧四舍五入,这样你就可以多出几加仑了你需要,不少...!最终,我们认为最好的前进方式是完全定制的引擎模型。实际上,我们已经开始在这条路线上进行启动/关闭、EGT、假脱机时间等 - 但要走得更远并正确地做到这一点,需要一些认真的工作,并且可能在一段时间内不会有成果。鉴于我们已经如此接近这些数字,因此在不确定的一段时间内(至少几个月)推迟似乎并不值得。坦率地说,在普通人看来,没有什么不对劲的地方,但你们离普通人还很远,不是吗?一旦发射后的清理工作平静下来,我们就会开始着手研究一个完全“Fenix”的引擎解决方案。我们还将仔细查看显示器。我们对它们也不完全满意,尽管这些问题是多么微不足道和美观(形状缩放、文本定位等)。但同样,我们想妥善处理它,而不是用胶带和祈祷。如果您不确定我在这一点上谈论的这些项目中的任何一个,它可以让您了解它们在事物规模上的相对次要程度。但是在这个社区中,透明度很重要,所以我宁愿谈论它,以免吓到某些人,也不愿忽视它。我们不仅将致力于上述工作,而且在开发过程中引起我们注意的数百个其他位在产品范围内无法证明......当时。对我们来说,发布的兴奋正在结束这一发展篇章,并开始一个全新的篇章。 “OOOOH LETS DO THIS”的列表每天都在增长。无论如何,在这方面少说多说,我们很兴奋。现在有很多关于我们如何在 sim 外部运行我们的系统的讨论,我们这样做了,但是我们也使用与 FSUIPC 和 Aerosoft 的 VGDS 相同的系统来自动为您处理这方面的事情。如果 MSFS 运行 exe.xml(自 SU9 以来,它有时一直在努力执行此操作 - Asobo 知道,但当它为大多数人工作时我们不会保留发布),您可以简单地加载 MSFS 并像其他任何人一样选择我们的 A320,去飞行,除了加载后的片刻,内部和外部系统执行瞬时握手,它就像任何其他飞机一样。如果 MSFS 决定不使用它自己的 exe.xml,只需在加载 sim 之前或之后的任何时间打开 Fenix 应用程序,它就会处理其余的 - 不需要其他任何东西。这种方法的优点很多,例如允许您选择要在哪个硬件上渲染显示,以缓解特定于运行它的系统的性能瓶颈。我们不处理序列号、2FA、带有验证链接的电子邮件等:只需下载安装程序并使用您用于购买产品的帐户详细信息登录即可。
- 只要您没有完全卸载 Fenix,就不会再次提示您登录或在 MSFS 之外执行任何其他操作。 关于这个系统有两点要记住: 1. 它需要在登录时连接互联网,但只要 Fenix 应用程序打开,它就会很高兴地离线运行。 2. 为简单起见,我们目前确实将每个许可证绑定到一台机器上,但一旦我们在乌克兰的同事恢复并运行,我们将把它扩展到 3 台机器并总体改进流程。 对于它的价值,您可以根据需要多次更换安装 PC,只需 ping 支持,他们会立即重置它,没有任何问题。
最后,当我们有发布日期和时间时,我们会尽可能多地发出警告。 我们对我们的基础设施充满信心,但我不承诺任何牛排晚餐。
-阿米尔
|
|