I get the backlog, but for instance click spots on the Carenado tablets have never worked properly, the door issue on the Spitfire has been around since release, and the Gee Bee R3 NOS doesn’t work. Those are just a few examples and you can’t tell me they are all not related to the testing environment. Unless MS/Asobo didn’t test them which we presume they did.
Backlogs are one thing but when updates have gone through and issues still aren’t fixed then there is more to the story. Just my 2 cents as an Xbox user.
well, it’s a multiple step process; first the author needs to fix the issue. MS/Asobo can’t do that for them. Then they need to supply the fix to MS/Asobo, who then need to check it, and push it. I believe the current holdup is with that checking process, which indeed, is slow and that’s frustrating.
Don’t get me wrong; I’m not making excuses here. Just trying to explain what’s going on for whatever that’s worth.
No I appreciate your input and enjoy the discussion honestly!
My only point was that to Xbox users it always seemed like something was a little off with certain add ons, but never showed up in testing due to this larger issue possibly(?). The DC-6 is so much more complex though that it really stood out, to put it simply (again assumptions, I don’t work in the tech field).
That being said, it’s a moot point now. Just wish this issue had been found earlier, if it is indeed more on a global scale.
I will be asking for a refund. I blame myself a bit. I should of knew better. Wisdom comes from making mistakes. My mother always said 'all lessons cost money. Thank heavens for the cheap ones.
The problem is not ‘no functioning controls and switches’. It is not a PMDG development thing.
This product have been working flawlessly for months for PC. In order to be working on Xbox it requires to be tested in something like ‘Xbox mode’ on devs PCs.
It has been tested in this mode and after passing all QC tests it was then submitted to Microsoft to be launched on Xbox marketplace. Right after launching problems apeared in the form of non functioning switches, controls and certain instruments. PMDG contacted Asobo/MS team to inquire about the problem.
Microsoft did reply to PMDG saying there was nothing of immediate action to be taken by them as it passed all QC in Xbox testing so this would require additional investigation. PMDG halted sales of DC-6 waiting for more information from Microsoft.
Robert Randazzo (PMDG) ended up informing through PMDG forum that apparently there is a difference between the Xbox Mode in SDK compared to Xbox ‘in the wild’. So he did tested as required by Microsoft but it ended up not working properly on consoles.
How come the Xbox Mode does not emulate 100% of Xbox consoles? It’s probably very frustrating for devs.
As per Mr Randazzo, this will require involving Xbox Team in Microsoft. This is the reason the solution may take a couple of months to get sorted out.
It’s somehow scary for developers to think they would work on Xbox mode to prepare their products to be available on Xbox marketplace and all of a sudden they do not work. Buyers can be frustrated and developers as well.
Microsoft did offer a refund for DC-6 (I did and I’ve got refunded in three days) which I see as a legitimate excuse, elegant stand and honest position.
Nobody was expecting this tough.
There is lessons to be learned and I’m confident they will solve this issue at some point and community will have access to this classic airliner.
Can we please please please get a rough estimate on when we can expect to see the dc-6 back in the marketplace? I haven’t heard anything new in about 25 to 30 days. I still have my dc6 that I paid $55 for in the marketplace on my series X with a gust lock I can’t disengage, tried with mouse tried with controller tried every way possible can’t disengage the gust lock which is probably one of the main reasons why it was pulled from the series x marketplace. But the plane works on PC just fine so what could possibly take so long to make the dc-6 work properly on Xbox I mean it’s not like you got to build a new plane from scratch everything’s already there you just got to fix it and make it work except this time, test it on Xbox before you put it on the marketplace .
Please read the forums, and the statement(s) made by PMDG with regard to testing on the X-Box prior to release.
This is not 100% on Asobo/Microsoft, but if blame is to be placed anywhere, the Fickle Finger of Fate is most assuredly swinging in the direction of the Pacific Northwest.
Actually I’m tinkering with it right now and I discovered the only way for me to get the Gust lock disengaged is to start my flight airborne. And yes I tried all the things with the AFE. But now even though I got the Gust locked disengaged still nothing works. The only things that really work are the rudder pedals (but the rudder itself doesn’t move), the carburetor heat, the trims, the exterior lights and interior lights, the flaps on the wings go down and up and the tablet itself works but the AFE menu doesn’t really do much, the beacon marker lights I think work and perhaps the propeller pitch lever. But none of the gauges work, the yokes don’t move, the throttle sticks don’t move, I can’t put my supercharger control on high LOL I can’t defrost the windshield, I can’t select an engine or start it (I can press RB and right on the d-pad to start the engines though or do it through the tablet), can’t control the cowl flaps or magnetos and one of the more important things I can’t control is fuel mixture. But I can move the armrests and the third seat lol. Also I can crack the windows open with my controller at the latch but then I have to use the touchpad on my keyboard to slide the window open. And there’s probably a bunch more stuff to list although everything on the ramp manager works which is cool. And it looks like the Garmin GPS nav system works, along with the ADF and the comms on the side of it. The autopilot works but I can’t control it. And there are quite a few more to list but enough is enough already LOL I’m sure pmdg is aware of all these things I’m sure they got a series X test bed lol. I’m going to be sure to check out that link though
Is there a performance update coming to PC for the DC-6? I read a while back that after SU5 the performance gains seen in other aircraft were not applied to the DC-6 and that kept me from buying it. Just wondering if there is an update expected from PMDG to apply the performance gains / fixes to the DC-6 also.
Im wondering the same thing. Although unfortunately it seems it’s up to Asobo to fix the issue as they have disabled a rendering channel for the instruments which is why the FPS is considerably lower in the VC than the exterior view. Some promising news is that during the SU5 beta it’s appeared that when that render channel was activated (for the beta) the FPS in the cockpit was the same as the exterior view. Saw a jump from 25FPS up to 65 FPS, everything worked fine too. Not sure why they have disabled it when they released SU5.
No idea why it may have been disabled, maybe crashes etc. I’d expect they’d reenable it at some point, maybe SU8? I’d say it’s likely been a low priority for them.
In any case you have a work around use it at your risk though.
The DC6 has the same performance as the default Cessna (and no I currently not running my supercomputer but only a Ryzen Generation 1 with on-board APU and no graphics card).
No “performance upgrade” is needed for the Cloudmaster.
That’s the complete opposite of my experience. The DC-6 runs as good as the default Cessna only if I’m using this trick described in dev mode. It brings my FPS from 32 to 55. And yes, 55 looks infinitely better and smoother than being capped at 30.
.