7 minutes ago, Wothan said:

Now 288 hours after last feedback from Ryan I still not have got any clear answer. Ryan just told that he don´t know, but doubt that it is intended if it´s scribted.

Cracking the throttles is necessary, but other than that the start always occure at the 12 blade call.

Finn,

As I literally just said, we prioritize actual support issues. If you cannot activate, or you are receiving some sort of error, or some other issue preventing you from using the product, we will ensure that those are taken care of within 48 hours (and usually a lot sooner), because we want to make sure people can use what they paid for.

Your ticket is entirely different. Ryan answered your question, albeit in generics, and that is the last thing on the ticket. If that wasn't enough of an answer for you, then simply respond to the ticket that you were looking for something more specific. When we respond to people, it pulls the ticket out of the active queue and marks it as 'waiting on response' - since you haven't responded, it's sat dormant in the 'waiting' queue. Again, since this subject isn't preventing anyone from actually enjoying the product, it's not as much of a priority (on top of the lack of indication that the answer provided was not enough for you - we can't read your mind).

3 hours ago, scandinavian13 said:

Finn,

As I literally just said, we prioritize actual support issues. If you cannot activate, or you are receiving some sort of error, or some other issue preventing you from using the product, we will ensure that those are taken care of within 48 hours (and usually a lot sooner), because we want to make sure people can use what they paid for.

Your ticket is entirely different. Ryan answered your question, albeit in generics, and that is the last thing on the ticket. If that wasn't enough of an answer for you, then simply respond to the ticket that you were looking for something more specific. When we respond to people, it pulls the ticket out of the active queue and marks it as 'waiting on response' - since you haven't responded, it's sat dormant in the 'waiting' queue. Again, since this subject isn't preventing anyone from actually enjoying the product, it's not as much of a priority (on top of the lack of indication that the answer provided was not enough for you - we can't read your mind).

I actually responded and Ryan told that the "issue" would be passed to the deveopler for them to comment, but I never got a comment from the devs.

I also got over it and has moved on, so no further actions expected from my side - I just wanted to comment on the post from Kyle, since I find that even the lowest prioritised issues or questions could be expected to be answered - at least that is what Im´used to from most other FS companies that I normally buy products from.

But please let it end here - there is no point getting into deeper discussions about this - I will be the looser of that discussion anyway and has learned to live with, and still enjoy, the DC-6 as it is.

 

5 hours ago, rampa said:

Starting the engines of this bird is really challenging every time, there is no way to make two starting procedures equal to another! May be PMDG has slightly exaggerated this aspect? Anyway if an engine refuses to start at all, my "trick" is opening more the throttle, about 1/2 or a bit more (corresponding at about more than 2000 rpm), and the engine starts, then reducing the throttle to the minimum rpms required for the warmup.

Claudio Rampini

I learned that I had to add more than expected throttles early during beta, and of course many things changed but not that.  I always line up the throttles such that the trailing edge of the levers are at the forward edge of a set of rivets on the pedestal.  That is close to 1000 RPM when the engines first start, although is is normal for the engine to catch and sometimes quickly get up to maybe 1500 but that throttle lever position I use is more than needed for 1000 RPM when the engines are warm.  For setting 1000 RPM on engines that have run a few minutes or more, I will set MP to just below 10 inHg or about 9.5 inHg and that seems to work every time, close enough that is.  None of this seems like an exaggerated expression of how the real thing behaves.

44 minutes ago, Wothan said:

I actually responded and Ryan told that the "issue" would be passed to the deveopler for them to comment, but I never got a comment from the devs.

Perhaps I was unclear earlier.

Ryan's response, that you reference here, is the last one in the ticket. He said he would pass it to the devs. To most, that response (particularly in light of the fact that it's not a bug) is good enough. Additionally, in the realm of social norms, if someone provides a response to a question, and gets no follow up, that's the end of the discussion. Should one want to discuss something further, a note to that effect would be the normal response. None has currently been received. That's what I was getting at. 

I want to bring that post up as I wonder also how deeply simulated the engine start is?

Do we have an answer to this (in my opinion) simple questions now?

 

Does overpriming/ to less priming affect start?

Does OAT affect starting?

 

 

Btw.: asking these questions does not mean, we do not like the DC-6 or that we thing PMDG has done an incredible job over all. It isn't even any critism. It is a wonderful addon. But it is just important to us, to understand the engines and take the right actions. Or, if just scripted, focus on other aspects. So, it would be nice, if Devs could just give a short and honest answer. Haven't found one till now in this thread unfortunately.

many tanks!

10 hours ago, guenseli said:

I want to bring that post up as I wonder also how deeply simulated the engine start is?

Do we have an answer to this (in my opinion) simple questions now?

 

Does overpriming/ to less priming affect start?

Does OAT affect starting?

 

 

Btw.: asking these questions does not mean, we do not like the DC-6 or that we thing PMDG has done an incredible job over all. It isn't even any critism. It is a wonderful addon. But it is just important to us, to understand the engines and take the right actions. Or, if just scripted, focus on other aspects. So, it would be nice, if Devs could just give a short and honest answer. Haven't found one till now in this thread unfortunately.

many tanks!

Hi Guenseli - long time since last we spoke :)

 

Exactly this is what I have asked for, but no real answer has been given.

I like the DC-6B, also if the engines are scripted - but some clear answer has yet to be given.

Hi, guys! Sorry for my poor english. Got a trouble with dc6 A and B. I'm starting engines as usual. AFE Before start. Then 3-4-2-1. Everything was ok till last week. Now i have no oil pressure after start, but i have a great white smoke from engines. Manifold pressure jumps up and down. Engines are serviced, oil quantity - full. This trouble comes each time i try to start engines after cold n dark. 

UPD: FSX, win7x64, core i7, 64Gb RAM... 

UPD2: Reinstallation of DC6 did not solve this problem...

7 hours ago, lightwriter said:

UPD2: Reinstallation of DC6 did not solve this problem...

That would of been news if it had, re installation creates more problems than it solves. What happens when you select 'Ready to Taxi' as the state?  Are the engines then running normally with oil pressure and MP as expected?

MP jumping up and down sounds odd, it should return to 30 inHg after a failed start and RPM should go to zero.  Do you show RPM when there is no oil pressure?  Sorry, unable to picture in my mind what you are seeing.

2 hours ago, downscc said:

That would of been news if it had, re installation creates more problems than it solves. What happens when you select 'Ready to Taxi' as the state?  Are the engines then running normally with oil pressure and MP as expected?

MP jumping up and down sounds odd, it should return to 30 inHg after a failed start and RPM should go to zero.  Do you show RPM when there is no oil pressure?  Sorry, unable to picture in my mind what you are seeing.

Ready for taxi. If ready for taxi everything is ok. MP, oil press, and RPM are ok. But for Air Hauler and loading cargo into aircraft I have to shut down engines. And starting is a problem. 

Jumping MP.  Engines do not stop. They are working. But working awful, as i described. I can make video of my engines startup))) 

I have no failed start. No MP 30 inHg. When no oil press RPM are about 800 - 1200. Rudders are set ba AFE.
 

 

Edited March 8, 20188 yr by lightwriter

Hi Finn, note they like our name on every post.

I understand that ready for taxi selection works, you only have problems manually starting engines.  I think I understand you say MP is erratic, RPM is 800-1200 and no oil pressure. I'm not sure what "rudders set by AFE" means, the rudder has nothing to do with engine start.

I don't understand how the engines do not stop so I am thinking something else is going on here that has nothing to do with the realism of the engine start. Please describe what you are using for throttle and propeller control, how are those controllers calibrated, and provide a full description of the "working awful" engine start:  MP high and low value, RPM high and low value, fuel pressure and describe throttle position and confirm propeller knob is full forward.

Downscc, sorry, not rudders, throttles.) they are set by AFE for start. I use saitek x55 rhino for throttles. Props are controlled by knobs in cockpit. No joystick assined to props. All other piston engines are working normal with this joystick. For example: A2A Boeing 377, A2A Constellation... Douglas worked too for a year or even more. Trobles with MP and oil press began last week. ( I'll record a video today. 

Ok, I've solved the problem. It is not dc6. It is not pmdg. It is not FSX. It was FS Flight Control addon. Beautiful moving map. Being started before FSX it does not allow start engines normally. I dont know why. If i start FSFC after eng start, everything is ok! 

Edited March 9, 20188 yr by lightwriter

5 hours ago, lightwriter said:

It was FS Flight Control addon.

Interesting.  Thanks for posting your finding.

Thank you for your answers and your help!) 

This week I bought the DC 6 and like many others started having problems with engine start. A bit weird because on first trial I was succesfull and had a good flight. Thereafter troubles began. However, I solved the problem and maybe others can benefit.

In the main FSX directory there is a folder called "PMDG" (yeah, what do ya know). There is a subfolder called " PMDG DC-6" and a sub-subfolder called "panelstate". In it there are two files: a .sav file and a .FLT file. Delete them both (don' t forget to make a backup).  

On my system everything is running well now.