Gilandred

I’ve been using SI since almost the beginning. While they’ve continued to add features (ground ops, copilot, cabin crew), I would consider the core atc program itself as inconsistent. Sometimes it works well, other times it completely misses the mark. The problem is you never know which version (the good or the bad) you’re going to get on each flight. I’m hopeful that all the work going into traffic injection is going to result in a more consistent end product.

Switch out the intel cpu for an amd X3D model. All of the benchmarks indicate it’s a better performing chip with lower power consumption. My next build will be similar to yours, with an amd 9800X3D. I’ll probably also up the psu wattage to 1200W.

I’ve been struggling with this too. Another example of control UI that makes zero sense, especially when the command is specifically called “enter aircraft” while in the sim. Hitting the button with your mouse, which highlights yet does absolutely nothing, is quite mind boggling as well.

The clouds and turbulence of XP are unmatched. I did a flight earlier from New York to Toronto in the Toliss A319 and it was pretty good overall. The layering and cloud colors look quite realistic. I’m using simheaven and you can tell it’s outdated, but it gives me better scenery than default. I’m now doing the return flight in MSFS 2024 in the Maddog, and let’s just say the clouds and turbulence leave a lot to be desired. Performance seems to be worse for me as well. I should note I fly exclusively in vr.

It should have been called early access. The pounding that Jorg and team are getting is well deserved.

I’ll probably make the switch once more of my aircrafts make the move (PMDG, Fenix, Dukes). I did fire up the maddog only to be confronted and mystified by the sim’s control setup. At one point I lost the ability to click anything in the menu. After changing keyboard setups I couldn't even find the “enter aircraft” command, which is ctrl-c by default. The barrier to entry was made unnecessarily high, especially for an old guy like me.

It’s hard to argue with such logical and persuasive counterpoints as “silly” and “absolutely ridiculous.” You win!

You argued that you should expect a discount for any further variant of the 777 series since the lion’s share of PMDG’s cost (ie. full price) was baked into the original launch variant. I merely presented an alternative viewpoint that PMDG is spreading the cost (and price) over all variants (current and future), and therefore no further discount should be expected. You might find that silly, but that is not an unusual concept in the business world.

You’re making an assumption that the 77W/F was “full price” to begin with. What if PMDG considered the future release of the 200 series in their overall pricing strategy and spread out those costs over the entire 777 series accordingly? In other words if the 77W/F were to be their ONLY products the price might very well have been $140 each as the “full price” of those products, and therefore paid a discounted rate originally. The first t-shirt you buy isn’t going to cost you $10 million because you have to pay for the t-shirt factory. The plan is to make many more t-thirts and spread out those costs so you are only paying $20 or so, even for that first one.

Their world hub concept needs to evolve so that it works similar to XPlane’s gateway system. Individuals can basically craft an airport to look almost like the real one, using a vast array of default assets. But then again, sales of third party airports would drop if the defaults look too good, so less money for Microsoft.

I reported a bug the other day and it was acknowledged by someone on the Laminar team (at least I assume he is on their team).

A weather radar in MSFS is mostly useless given the current state of their weather system. I never see towering thunderstorms at the higher flight levels, passing through “red” areas is barely noticeable, and I never worry about hail or wind shear if they are even modeled. I’d rather Asobo focus on this first, or even better, turn the weather over to another developer who knows what they’re doing.

Ok just submitted and put in some more detail. It would be great if chaseplane could take control of the vr reset function just like any other custom view. As it stands now, that is currently established and controlled within the default sim camera.cfg file using precise xyz coordinates. Thanks for looking into this!

I’m weak and ended up buying anyway. Unfortunately the vr reset does function the same as the default camera. Any change will change the reference point for all other camera views. HOWEVER, the UI and everything else is head and shoulders above the default! ‘The wiki mentioned that the mouse cursor bug appears in all but the default view. What exactly is the default view, because I’m getting this issue regardless of what view I select?

Thanks. It sounds like you guys have fixed my main issue. I might wait until the mouse cursor issue is fixed though before buying if you’re able to figure it out.