Carrier Script Test

[fargo007]

What does the 1.2.1 Menu issue involve?

 

I am seeing a problem where whenever carrier wrench is loaded, it makes the menus created with other scripts no longer appear.

 

Is this a related issue?

 

The only thing that makes the menus reappear is NOT loading carrier wrench at all.

 

Even if it's loaded on a time_more of 300, any clients joining after it loads get no menus at all.

Edited February 20, 2019 by fargo007

[Sadist_Cain]

I don't believe that (for me at least) the F10 issue is specific to the carrier script, I've had my F10 menus disappearing for clients whenver I simply add a ship to Through The Inferno.

 

Still trying to figure it out, it seems that when a client loads the mission quicker than the server they can access the menu, that's all I've got so far.

[tekrc]

I tried following the instructions but I just get this error when i load the mission

what broke?

Edited March 15, 2019 by tekrc

[Wrench]

That's an old naming convention for the script call. Check the .Lua file for the updated name

[tekrc]

That's an old naming convention for the script call. Check the .Lua file for the updated name

 

that is from the script file.

just fresh copy pasted the bit at the top of the script file and changed the names and numbers. same error.

Edited March 19, 2019 by tekrc

[tekrc]

can I get the part I need then? the file I downloaded (now 3 times) uses the "old naming convention" and I dont see a newer version than 1.2.1 which is what I got

[SkipperSMG]

can I get the part I need then? the file I downloaded (now 3 times) uses the "old naming convention" and I dont see a newer version than 1.2.1 which is what I got

 

 

You named your Carrier "Stennis_AI". However in the script only "Stennis" is declared, so you have to add more names or change the default in the lua. Open the file and search for "Stennis". The rest is self explanatory :smilewink:

[SkipperSMG]

I would also like to point out that the carrier script removes my F10 radio options in MP with Version 1.2.1. for DCS 2.5.4.29079. I get it to show up by starting the mission triggered by a client joining, which coincides with what others have reported here. However the menu appears to be not functional. When selecting commands the text messages show up correctly, however Nothing happens. The base script however works. Carriers are turning into the wind and pursue their task.

[Wrench]

I'm working on rewriting the script more or less from scratch right now.

I'll be out of town for a few days, but I'll keep you guys posted.

[SkipperSMG]

Thats awesome to hear :) keep up the good work and take your time.

[Wrench]

Version 2.0a released! Check first post.

[Thewarblade]

Version 2.0a released! Check first post.

Many Thanks Wrench.

 

 

Gesendet von meinem SM-G935F mit Tapatalk

[mcfleck]

Incredible! Cannot wait to give it a try. Thank you very much wrench

[lucky-hendrix]

Shouldn't this thread be in the mission editor section rather ? Thx for the script very useful!

 

Sent from my VTR-L09 using Tapatalk

[LURKINGBADGER]

Great stuf that script, thx very much.

 

I set it up no problem in Caucasus, but it keeps saying ''turning to brc'' in Persdian Gulf, it is the exact same setup.

 

Is there an issue in Persian Gulf?

wrenchscript test persian.miz

[jmarso]

What's the difference between the carrier script and the wrench functions script?

[Wrench]

That file is a collection of scripts I wrote to handle some other tasks, like respawning/controlling the drone fighters in the demo mission. It's not needed for the carrier script to function.

[jmarso]

Cool deal. Domo arigato!

[DMAN67]

Total noob question...I've searched this thread and others but have no clue where to install the Carrier script within the DCS Scripts folder. Can someone please explain? Thanks in advance.

[mono6020]

hi,

i use this carrier script on a dedicated server for a carrier group with stennis, 2 ticonderogas and 2 perry class to be able to stop and start the group on command.

after 1-2 days in automatic mode (or even if commanded to stop for a day or two) the carrier group stops moving. it doesn't move in automatic and even in override mode. does anyone know why? do the 4 support ships run out of fuel? is there anything else that could cause them to stop and never move again?

would be happy for any tip/suggestion.

[Wrench]

Hm, I've never really tested it for that long, but there's no real reason the script shouldn't continue to work. Can you post your server's log file so I can have a quick glance at it?

I've actually pretty much concluded my development of the script itself, given that the guys at the MOOSE development team have made the airBoss do pretty much everything that mine does, only better, and with the supercarrier on the horizon, even that may not be needed for long.

[mono6020]

yes we tried to work with airboss class too, and while it is a great and fancy class and has lots of cool features, we prefer the more simple and flexible approach of your script with the ability to start and stop the carrier at any time as well as the override and automatic feature. we like that a lot! that's also the reason we use 1.2.1 version, as it seems you have removed the manual controls with the later versions.

unfortunatly i dont have the server logs from that specific session. what we did now is to put the Stennis in a single unit group and remove the support ships as a test. it runs since yesterday and we will continue to monitor the carrier movement. if the sudden stop happens again i will of course provide you the server logs.

thanks for your time and the great script!

[Wrench]

Glad to hear it! Next time I'm at my main PC I'll have a look at reenabling those controls for you guys.

[mono6020]

hey there,

so we tried a few things. unfortunatly the carrier always stops moving after >1 day, no matter if single unit or multiple units in a group. we tried the following:

 

- carrier in automatic mode all the time: stops after approx. 30 hours

- carrier in automatic mode only for launch and recovery (stopped in between): after the last stop command (approx. 48 hours after start) it never resumed movement neither in auto nor override

- carrier always in override: worked for 8 hours straight then we had to go back to auto to bring the carrier away from coast. after that same as nr. 1

 

i suspect something related to dynamic weather. we have noticed the wind changes direction and speed several times over a few days and so changes the BRC of the carrier. also sometimes the carrier reports "-1" if asked for current BRC which looks odd. what do you think?

server logs attached although we couldnt find any clue in there but maybe it helps.

greets

dcs.log.txt.zip

[Pikey]

Pretty good logs for over a day running. They were clean, not spammed and without error bar the RAT object.

 

I strongly suggest the problem is in DCS running the game for that long. Carriers do stop if they detect an obstruction, and you lose access to the controllable, that was reported ages back, especially happens when the escort crosses path. With dynamic wind anything could be happening, but from the logs, it's not scripting.