[DCS BUG] Shaking in the backseat while on the carrier in MP

I guess the problem of shaking in the backseat while standing on the carrier with running engines on multiplayer seems to be an ED netcode issue.

Thats why I posted it here:

https://forums.eagle.ru/showthread.php?t=246602

Unfortuantely, I guess it does not get enough attention over there, thats why I re-post it here and hope to get some more attention over there.

:pilotfly:

Noted.

As it seems, this issue needs to be reported directly from Heatblur to ED.

Please do so, thank you.

Heatblur,

have this been reported and brought to attention by you to ED as Bignewy has told?

I can't believe that no one else brings this on the table.

The Tomcat is a multicrew carrier aircraft, and it is not possible to hit a single button in the backseat. This is a big problem in the key feature of that aircraft...

So this bug is still present?

It's impossible to click anything.

It's worst than an earthquake in the backseat. Very annoying and unhealthy.

Still present, unfortunately, very annoying :-/ :

I-LV6A3ManE

Are there any news on that topic from the Dev side?

+1 As soon as engines are running the shaking starts.

Any operation on h backseat is then impossible until lift of...

Please fix.

You guys get that this is because of the terrible code of the carrier by ED not anything to do with HeatBlur right?

Their time would be better spent finishing the Forestall than trying to fudge the outgoing placeholder carrier ED doesn't even care about anymore.

I am only a user not a coder or a program expert...

Fact is that the F-14 RIO seat on a moving carrier is not useable and that should be fixed as soon as possible.

You guys get that this is because of the terrible code of the carrier by ED not anything to do with HeatBlur right?

 

Their time would be better spent finishing the Forestall than trying to fudge the outgoing placeholder carrier ED doesn't even care about anymore.

I don't care who is responsible and I don't care about the reason, I just want to get it fixed to be able to startup the F-14 from the carrier without getting seasick.

Read again post. nr. 3.

Heatblur says, that it is EDs fault, and ED says that they can't do anything about it as long as Heatblur does not bring it up to ED.

So, they are both pointing at each other and let us in the dark. Probelm is existing since the F-14 got released, so over an half year later, at least an statement of the actual situation would be be highly appreciated.

The F-14 hasn't been released. It's in Early-Access. Same with the F/A-18 which also has issues on the carrier and technically the Carrier itself is Early-Access since it's just a place holder for ED's "real" supercarrier they rushed out to go with the Hornet Early-Access.

And review the post yourself. They aren't saying HeatBlur hasn't reported it, they're "Neither Confirming or Denying" that it's a known issue at ED.

Edit: Also https://forums.eagle.ru/showpost.php?p=4118444&postcount=12 Months to respond. MONTHS.

Good if you are fine with it as it is.

I would like to use the Tomcat as it is intended to.

To do so, this bug needs to be fixed. At least it would be nice if the Devs would let us not sit in the dark regarding that topic.

Good if you are fine with it as it is.

 

I would like to use the Tomcat as it is intended to.

To do so, this bug needs to be fixed. At least it would be nice if the Devs would let us not sit in the dark regarding that topic.

It does not prevent you from using the Tomcat as it is intended to at all, hence this is not a gamebreaking bug, although definitely a pretty annoying one. And I agree, I would also like to know if ED is actually aware of this. That's also the reason why I would love to know if this bug is present in the L-39 too. I can't test that myself, as I don't own the L-39.

It does not prevent you from using the Tomcat as it is intended to at all, hence this is not a gamebreaking bug, although definitely a pretty annoying one.

You can't use it as it is INTENDED.

Intended would mean, to be on a moving carrier, crank up the turbines, set the air source to both and THEN turn on the cooling in the backseat and start up the WCS and begin aligning.

If the WCS will be turned on before getting cooling air from the turbines, it would get damaged quite fast. So the workaround we need to use at the moment is, to accept that this would break the system IRL.

Fine if you don't want to use it in a realistic way, but I would like to do that as DCS is designed around realism.

And I would like to prevent the RIO from useing the comit bag even before the plane got in the air. its so worse in VR...

And I agree, I would also like to know if ED is actually aware of this.

My patience in the whole DCS enviroment is getting overused more and more, but It would be easier to wait for a fix if we would know what the situation is. At the moment we know nothing, except that HB is pointing at ED and ED is pointing at HB. That makes me more sick than being RIO on a moving ship.

As you can see, ED also pays no attention to that situation.

That's also the reason why I would love to know if this bug is present in the L-39 too. I can't test that myself, as I don't own the L-39.

Maybe you'll find someone who have spare time to do something like that, record it, report it and wait months for no answer. I'm not gonna test that.

ED isn't pointing at HB, they're just being obtuse. They never said HeatBlur did or didn't already tell them about the problem. Their response was all business weasel words. At least HB is telling you the truth even if it's disappointing.

Thing is, why would ED fix their carrier when they are about to have a fancy new carrier to sell you?

HeatBlur is doing more than their part by creating a completely other carrier. Would you rather they stopped work on the forestall to put more energy in trying to get ED to fix their abandonware carrier? Because you can bet the Forestall is going to work fine the way the F-14 is coded now AND is included in the price of the F-14.

And I'm not OK with it, that's why I don't trust "Early-Access" any more than any other pocket full of mumbles promises.

You can't use it as it is INTENDED.

 

Intended would mean, to be on a moving carrier, crank up the turbines, set the air source to both and THEN turn on the cooling in the backseat and start up the WCS and begin aligning.

If the WCS will be turned on before getting cooling air from the turbines, it would get damaged quite fast. So the workaround we need to use at the moment is, to accept that this would break the system IRL.

Fine if you don't want to use it in a realistic way, but I would like to do that as DCS is designed around realism.

And I would like to prevent the RIO from useing the comit bag even before the plane got in the air. its so worse in VR...

You can use it as intended, meaning as you described. It's not very easy (hitting the correct buttons) or pleasent (endure the shaking) to do so, but it is very much possible. So it's not gamebreaking at all, as you can either workaround it, or go through it. It's just annoying/unpleseant.

Indeed it is extremely annoying. Hopefully we can find a solution for this soon, but I will be honest: at the moment we were not able to make any progress on that - which just means we need to keep trying. And we will.

Sad to hear, but thank you very much for the information and trying!

Nearly a month later, any news on that issue?

As far as I know, the wheelchoks are not yet implemented in the F-14.

Would those maybe a workaround solution until the sliding is fixed in general?

(To finish the whole start-up procedre until taxi'ing without shaking)

I was really stunned to see, that the RIO shaking is not present on the new SC! It was such a delight to operate on the carrier as a RIO, without getting thrown around in the cockpit! Really enjoying it! :)

I haven't tested yet, if this issue might also be fixed for the Stennis now.

ED finally figured out whatever was causing that. Good to hear.