Jump to content

Recommended Posts

Posted (edited)

Okay, I'm at my wits end with this. On the 107th server, and semi-regularly, CAINS will not stay on.

 

I've got the right datalink freq for the carrier I'm on as stated by the kneeboard.

Datalink Power set to ON

Parking Brake ON.

 

I flip the CAINS switch and it goes right back to off again, and I cannot align using the system.

 

I quit out, and my pilot can get Jester to do it.

 

What am I doing wrong or is this a bug? It's about a 50/50 shot that it'll work in any given carrier based jet.

Edited by IronMike
Posted (edited)

Been on non-dedicated servers and not had this problem. This includes returning via respawn in a new jet.

Edited by Eihort
  • 4 weeks later...
Posted

Well I can't even get it to work with a relog/restart of the client now, so multiplayer 'catting from a boat is pretty much unplayable unless you want incredibly lousy INS fixes.

  • 3 months later...
Posted

I gotta say, this bug is really destroying carrier operations with the Tomcat for me. While I didn't really have this issue in the first few months after Tomcat release, I now have it more often than not.

 

Yesterday I tried to host a Tomcat coop mission and that damn CAINS switch just didn't want to stay in place. I restarted the mission 5 times, because in the past it sometimes worked after a few restarts, but this time it just wouldn't work at all. :mad:

 

Is there anything once can do to increase the chances that the CAINS switch will stay in place?

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted
Unknown to me at the momen, QuiGon, we will investigate.

Hmm, that really makes we wonder how widespread that issue is. Would a track or log file be of any help here?

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted
Hmm, that really makes we wonder how widespread that issue is. Would a track or log file be of any help here?

 

Absolutely, please if you would be willing to do that it would be most appreciated. Tracks for our devs are not only "watching what happened" but they can actually look at what happens in the background. As always, the shorter the track, the more reliable, most reliable if it is a server track that does not equal the client.

 

Thanks a ton in advance!

Heatblur Simulations

 

Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage.

 

http://www.heatblur.com/

 

https://www.facebook.com/heatblur/

Posted
Absolutely, please if you would be willing to do that it would be most appreciated. Tracks for our devs are not only "watching what happened" but they can actually look at what happens in the background. As always, the shorter the track, the more reliable, most reliable if it is a server track that does not equal the client.

 

Thanks a ton in advance!

Yeah, in most cases this is not really something I can provide as I mostly fly on very busy public servers, where a bug occurs after several hours of playing. In this case though it's a small private hosted mission and the bug occurs at the very beginning, so I will be able to provide a track. Besides my own track (host + RIO) I can also provide my buddy's track (client + pilot). Speaking of that, we can actually do some testing if it makes a difference if we switch roles in the cockpit. :joystick:

 

I will report back later!

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted (edited)

Alright, we tried a couple of things yesterday:

 

First I created a quick empty test mission, with only a carrier and a cold start Tomcat on it. My buddy and I tried to do a carrier alignment there and it worked just fine. The CAINS switch worked as it should.

 

So then we went back to the mission where we had the problem and there it happened again: The CAINs switch just wouldn't stick to the forward position. We tried to switch slots, so that my buddy (client) would be the RIO, but same result.

I attached the track file from him of this attempt, so you have a trak from a RIo who is not the server host. He's not familiar with the RIO role, so I had to talk him through the steps in the cockpit.

 

Now, this results makes me wonder, as it seems to be something in the mission that caused this. The mission was actually a cold start & coop beta of mission 3 of the now official Cage the Bear campaign, which kaba did send me to test it out. I mentioned in my earlier comment, that I did have this CAINS switch problem a few months ago already. This happened when I hosted another coop mission, which happened to be mission 1 of the very same campaign, which wasn't an official campaign back then and was editied by me to make it playable as a coop mission. Back then it wasn't just me and my buddy having this problem, but also the guys in the second Tomcat that flew with us back then. So something seems to be fishy with those campaign missions that causes this problem. I also attached the mission file, so you guys can give it a try and see if it happens to you as well.

CAINS bug.zip

CAINS bug mission.zip

Edited by QuiGon

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...