Tomcat Supercarrier is Broken

Many problems for me

Ground crew comms for Request Launch elicit no response. Taxing behind the JBD and waiting does nothing. No wingfold signal. Only when I continue to taxi over the JBD does the deck crew finally animate. Blackouts on 50% of launches so can't go to AB during the stroke.

Please help

One of the great things on the forums is people being able to express themselves. One never knows when a useful comment will answer a vexing question.

But really, when someone reports a bug post and asks for help, answering with "open beta, early access" comes across as "you idiot, don't you know...."

A far better response (for both the poster, others and the devs) would be things like "I'm not having those same problems", or "have you tried xyz.."

Just saying.

i had that problem 1st time but not 2nd

One of the great things on the forums is people being able to express themselves. One never knows when a useful comment will answer a vexing question.

 

But really, when someone reports a bug post and asks for help, answering with "open beta, early access" comes across as "you idiot, don't you know...."

 

A far better response (for both the poster, others and the devs) would be things like "I'm not having those same problems", or "have you tried xyz.."

 

Just saying.

I agree. Every single comment is appreciated here, no exceptions. Sometimes we might argue, sometimes we might agree, sometimes and most most often: it will help us fix issues. That is why, no matter what, we appreciate every comment, remark, etc or in general feedback you guys have for us.

Furthermore, all your input translates to me as passion for our product. Even what Trev posted, while not of the kind nature, heh, it comes from passion. That is what connects us all here. So please be kind to each other.

I will answer the initial post shortly, I did not overlook it, I am currently running a couple tests to have a best answer.

Many problems for me

 

Ground crew comms for Request Launch elicit no response. Taxing behind the JBD and waiting does nothing. No wingfold signal. Only when I continue to taxi over the JBD does the deck crew finally animate. Blackouts on 50% of launches so can't go to AB during the stroke.

 

Please help

It seems at the moment sometimes you only get accepted at the cat that is assigned to your spawn point. Unfortunately you have to go from cat to cat to see which one will accept you, ED is aware.

There is no wingfold signal, only wingsweep for the Tomcat. Whether or not ED will add it we do not know. Simply sweep your wings when taxiing over the JBDs.

As for the blackouts: would you have a video or a track for us please? Not sure what is happening there.

Had a blackout on take off, that I seem to have forgotten to have put the flaps down. Perhaps that is it.

Ive had problems with not communicating with the ship in multiplayer. It wouldnt work at all trying to get permission to start, despite being able to listen to other players go around the ship. Ive had occasional problems where Ive had to have jester select the radio twice before it would work, but this time it didnt work at all. Might be finger trouble on my part of course, its happened before.....

Is CATIII glideslope broken? I though it was the ACLS that was broke, but I was using just the needles and although I was on approach, I damn near flew into the water.

Not being critical I might add, just chalking up my experience. A it is, the cat 1 approachs work fine, and flying this with the supercarrier is about the best experience ive had in simming in years.

I’ve had the blackout on launch issue occasionally as well.

Though I haven’t extensively tested, my initial impression is it seems to happen more when the aircraft is heavy (6PH loadout or lots of bombs).

I’ll see if I can do a track today if I can reproduce it, but I’ve had bad luck with tracks lately...

 

There is no wingfold signal, only wingsweep for the Tomcat. Whether or not ED will add it we do not know. Simply sweep your wings when taxiing over the JBDs.

I wouldn't mind getting the wing unfold signal as substitute for a wingsweep signal. That would be enough of a reminder.

Removing the signal to retract the launchbar would also be nice. I occasionally forget to ignore it.

IIRC, if you're blacking out because your in burner on launch, that may be a feature, not a bug. IIRC, IRL the -B never used burners on launch because the engines produced so much thrust it would over speed the shuttle in burner and cause damage to the mechanism. I never use burners on cat launches and have never blacked out on launch. Could be correlation and not causation but no burners is the IRL procedure to my knowledge.

Sent from my Pixel 3 XL using Tapatalk

No, never used burners on on launch, and ive only ever had it happen once on the no1 CAT when I didnt use the flaps.

Im idly wondering if sea state might be a partial explanation.

Many problems for me

 

Ground crew comms for Request Launch elicit no response. Taxing behind the JBD and waiting does nothing. No wingfold signal. Only when I continue to taxi over the JBD does the deck crew finally animate. Blackouts on 50% of launches so can't go to AB during the stroke.

 

Please help

About the blackouts, did you eat before take off?

Jokes appart, the blackouts occured top me when I wasn't well aligned with the catapult. With SC I managed to align better and this problem stopped. Check if this is the problem

I’ve had the blackout on launch issue occasionally as well. ... .. . .. ... I’ll see if I can do a track today if I can reproduce it, but I’ve had bad luck with tracks lately...

Same for me, happens sometimes here and there.

I am never using AB when flying off the deck, no matter of payload.

After reading this thread, I will make notes of payload when it happens.

I got one.

MP mission started via the mission editor.

Takeoff from Stennis.

Payload:

Video: https://youtu.be/yo02NNRH_3c?t=78

I attached track file of cat blackout

Also the AOA and fuel flow indicators fluctuate during startup, not sure if intended

I too have trouble with Request Startup comms to the carrier, must do it twice before getting a response

catblackout.trk

In my first hour of trying Tomcat with SC I was once blown up staying connected to the cat after some wobbling.

Many problems for me

 

Ground crew comms for Request Launch elicit no response. Taxing behind the JBD and waiting does nothing. No wingfold signal. Only when I continue to taxi over the JBD does the deck crew finally animate. Blackouts on 50% of launches so can't go to AB during the stroke.

 

Please help

As others says its all WIP...

But the request launch won’t give you any feedback or radio response.

If the crew is in recovery position, with request launch you will have them deploying for launch (assuming that there are no recovery operations otherwise you won’t be able to use cat 3 and 4).

That’s all

It seems at the moment sometimes you only get accepted at the cat that is assigned to your spawn point. Unfortunately you have to go from cat to cat to see which one will accept you, ED is aware.

 

There is no wingfold signal, only wingsweep for the Tomcat. Whether or not ED will add it we do not know. Simply sweep your wings when taxiing over the JBDs.

 

As for the blackouts: would you have a video or a track for us please? Not sure what is happening there.

I found in MP that say if you are spawned near El 1 (ahead of the island), you can choose either cat 1 or cat 2. Whichever one you approach, they will activate without having to request launch.

I concur that there is no wingfold/wingsweep signal. Be aware of this. I once launched with my wings folded. If I realized beforehand or used a checklist, it would not have happened. Good news was that I was still able to launch and climb safely (in full AB).

v6,

boNes

Still blacking out on launch but some things are fixed.

Yellow shirt now tells me to unsweep wings and no more raise launch bar animation. FF and AOA jitters are gone

But new lighting is terrible, must hotfix

blackout2.trk

We cannot hotfix the lighting that is ED side. Tweaking the lights back takes a lot of time, and we cannot do this for every patch. We need to wait until ED is finished with their tweaks. In the meantime pls turn the lights down. Thank you for your kind patience.

The lag spike that leads to blackouts is also something on ED side, we've made them aware of that. You can see it sometimes in F2 as well, also for hornet and on the kunzentsov, too.

i didnt have it at all for the 1st few days, now i get it every launch lol, also i found out you can launch with wings swept and a decent combat load on easy enough ooops lol

IIRC, if you're blacking out because your in burner on launch, that may be a feature, not a bug. IIRC, IRL the -B never used burners on launch because the engines produced so much thrust it would over speed the shuttle in burner and cause damage to the mechanism. I never use burners on cat launches and have never blacked out on launch. Could be correlation and not causation but no burners is the IRL procedure to my knowledge.

 

Sent from my Pixel 3 XL using Tapatalk

Where did you read that rationale? damage to what mechanism? Need a source for that.

No AB for the F-14B takeoff due to one-engine out controllability margin is the rationale I have seen quoted numerous places.

No AB for the F-14B takeoff due to one-engine out controllability margin is the rationale I have seen quoted numerous places.

Correct. The Blackout/lag spike on spawn even sometimes, is not a feature.

We need to wait until ED is finished with their tweaks.

Please no, i beg you

Please no, i beg you

Sorry golden, it is just not possible. We would be doing nothing but tweaking lights between each patch, we cannot do that. :(

Sorry golden, it is just not possible. We would be doing nothing but tweaking lights between each patch, we cannot do that. :(

Understandable.

Hm ... just thinking ... a way ED fishes for pilots in the pool of HB customers in order to have them buying THEIR modules instead of HB modules? No, that is a stupid idea, and pure speculation ... "God da.n Maverick!". Maybe its just bad comms or bad programming on ED's side, or shifting priorities because every single location in ED's code is currently under construction :music_whistling:

We'll have to wait I guess ... so let's be patient folks. Me saying ... :D