M.Muir

I tested it right after patching this morning. No changes. Still the same issue. Also I tested it on Single Thread. Not Multi.

Awesome. I will test it as soon as it drops.

Both. First thing I tested when I had issues was to switch modes thinking MT might have been the issue, but the issue happens across both version. Mind you that was with me testing it on Mission 12 only. I did not try that on mission 13, but I figured the issues might be similar at that point. :EDIT: I went back in Single Thread, and started up every mission again to double check since I thought I might have had a similar problem on a Earlier mission, but everything checks out, Audio starts with in 30 seconds of mission start. There is sometimes a delay that causes dialogue to overlap, but it fixes itself. I couldn't test the Entire Mission, but from what I have see. The Bug with Mission 12 and 13 shows itself at the beginning of the mission.

On top of Mission 12. Mission 13 is also showing the same issues.

I just got to mission 12, and there is no dialogue or music. I checked the radios, and the volume knobs weren't turned down. So I'm not sure what I can do to fix it on my mind. Love the campaign by the way, so hopefully there is an easy fix. Maybe one I can do.

Can confirm. I'm having the same issue too. Nothing happening after the IR missile launch.

I'm having the same issue, but on my dedicated server only. When I play the mission locally it will work, but when I play it on the server. I spawn in the air. I know some others were having that same issue too but it was fixed by making sure the module was installed or reinstalling. That being said I have the module installed both on my PC and on my server.

I stayed up all night waiting to update my server and still no update REEEEEEEEEEEEEEEEEEEE. Kidding. I was up working on other things while waiting. You all take your time, I rather it be late and working than rushed because people want it now, but broken. So thanks for the work!

W̶h̶e̶n̶ ̶y̶o̶u̶ ̶s̶a̶y̶ ̶M̶o̶o̶s̶e̶ ̶P̶o̶r̶t̶a̶b̶l̶e̶ ̶d̶o̶ ̶y̶o̶u̶ ̶m̶e̶a̶n̶ ̶M̶o̶o̶s̶e̶-̶u̶p̶d̶a̶t̶e̶1̶2̶1̶5̶.̶l̶u̶a̶?̶ ̶ ̶I̶ ̶a̶m̶ ̶i̶n̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶b̶o̶a̶t̶ ̶a̶s̶ ̶T̶i̶p̶p̶i̶s̶,̶ ̶b̶u̶t̶ ̶I̶ ̶t̶r̶i̶e̶d̶ ̶t̶h̶i̶s̶ ̶l̶a̶t̶e̶ ̶l̶a̶s̶t̶ ̶n̶i̶g̶h̶t̶.̶ ̶A̶d̶d̶e̶d̶ ̶e̶v̶e̶r̶y̶ ̶u̶n̶i̶t̶,̶ ̶o̶r̶ ̶I̶ ̶t̶h̶i̶n̶k̶ ̶I̶ ̶d̶i̶d̶,̶ ̶a̶b̶o̶u̶t̶ ̶t̶o̶ ̶d̶i̶v̶e̶ ̶b̶a̶c̶k̶ ̶i̶n̶ ̶a̶n̶d̶ ̶d̶o̶u̶b̶l̶e̶ ̶c̶h̶e̶c̶k̶,̶ ̶b̶u̶t̶ ̶I̶ ̶t̶h̶i̶n̶k̶ ̶I̶ ̶a̶d̶d̶e̶d̶ ̶e̶v̶e̶r̶y̶ ̶u̶n̶i̶t̶ ̶n̶e̶e̶d̶e̶d̶,̶ ̶y̶e̶t̶ ̶w̶h̶e̶n̶ ̶I̶ ̶l̶a̶u̶n̶c̶h̶e̶d̶ ̶t̶h̶e̶ ̶m̶i̶s̶s̶i̶o̶n̶ ̶Z̶e̶u̶s̶ ̶d̶o̶e̶s̶n̶'̶t̶ ̶w̶o̶r̶k̶.̶ ̶A̶l̶l̶ ̶t̶h̶e̶ ̶o̶t̶h̶e̶r̶ ̶s̶c̶r̶i̶p̶t̶s̶ ̶s̶u̶c̶h̶ ̶a̶s̶ ̶m̶i̶s̶s̶i̶o̶n̶ ̶s̶p̶a̶w̶n̶ ̶w̶o̶r̶k̶,̶ ̶b̶u̶t̶ ̶w̶h̶e̶n̶ ̶I̶ ̶t̶r̶y̶ ̶t̶o̶ ̶s̶p̶a̶w̶n̶ ̶v̶i̶a̶ ̶Z̶e̶u̶s̶ ̶n̶o̶t̶h̶i̶n̶g̶ ̶h̶a̶p̶p̶e̶n̶s̶.̶ Edit: Found the issue. While I had all the units and names right. A few of the units had an unneeded space at the end. Lesson of the day. Don't mess with the editor at 3am. Also I want to thank you both for the fun mission, but also the inspiration. I hope you don't mind, I am a complete novice at scripting or code in general, but your mission design has kind of sparked my interest. So I have spent the last few weeks trying to learn how it works, and doing some tweaks or experiments.

I've enjoyed the PG, but my suggestion for an improvement would be this location. Quasoura Airfield Image 1 Quasoura Airfield Image 2 Quasoura Airfield Image 3 Quasoura Airfield Image 4 Google Maps Image I wouldn't want it fleshed out, but personally since the airfield is there. I would like to see it as a possible spawn point for aircraft. Leave it as is, don't model the terrain, but give it parking spots and a name for AI to take off and land at. It would be great for scripts like Random Air Traffic, but it could work for other uses. Even in it's current state.

Yeah now the question is which one. I guess we have to look at what we know. There is a body of water near the end of the run way, and a few interesting parking and taxi way designs. EDIT: Seems like the image with the Taxi way and water is Ramat David in Israel So I doubt it is the new map.

Hmm. That is a good theory. I know one of the images was claimed to look like Syria, which we know isn't free. These three look like Nevada Test Range. Image 1 Image 2 Image 3 Finally there is this one with a slight view of the Runway. Looks like it could be caucuses but the buildings are different. It's not Nevada. I think I am going to go look in game, and try to find that airfield to make sure. EDIT: Seems like the image with the Taxi way and water is Ramat David in Israel So I doubt it is the new map.

I have my 56 on 3.0 slots. Some people recommend getting a powered 3.0 hub, but I haven't needed it.

Yeah it is like I said earlier. They use a grease to on the throttle to keep it lucubrated up. I find that with a little bit of use it gets easier to move, but it isn't too bad, and you get use to it. But even before it loosens up it isn't bad just takes a little bit more force. After a while you won't notice it. That being said. I know some people open up their throttles and use a third party grease after removing the old, but I think that voids warranty. I might do that once I am out of my three years and if I am still using it. And it isn't too hard to change the springs. You will see how it is done when setting up the stick for the first time. I personally went with the strongest spring and it has been great.

Internally it apparently has better components. When I got mine I made sure to get the Logitech ones because compared to the Madcats 56s they seemed to be better built, but it is hard to tell component wise between the 55, and 56 without opening them up. I went from a 52 pro to my current 56, but compared to a buddies 55, it doesn't seem too different. Plastic did seem nicer. Externally, the only real change is the mouse nub on the throttle, and hat switch swapped out for a game pad style thumb stick. Also I think the springs are different. But if you are going to get one of the X56 sticks. I would go for the grey Logitech ones, and avoid the 55 or blue 56s. They are newer, under warranty, and will be supported. That being said. I would recommend getting an external warranty for any Hotas. I got mine via Amazon, and picked up a three year warranty for about 10 bucks or maybe less. As for the sim itself. I would say the Logitech 56 is better for the sim ONLY because of the support from Logitech. They are still updating the software, where as the older software is no longer supported. Both designs the 55 and 56 should work the same.

Yeah. The X-65 is 2010 and not in production anymore. The Grey Logitech is the newest of all three. Also the Rhino name is both the X-55 and X-56. Also the Throttle does take a little time to loosen up due to the grease used to lubricate the throttle (Logitech version at least), I don't find it hard to us, it does take a little bit a force, but nothing you shouldn't get use too. That being said I would recommend something under it to keep it from slipping if you have a slick surface.

X-55 is Saitek when owned by Madcats X-56 with blue decals is Madcats and maybe early logitech. X-56 with grey decals is logitech X-65 I am not 100% sure if it is pre-Madcats Saitek, or made during Madcats, but it isn't Logitech. Difference wise. The X-56 has game pad styled sticks compared to the 4 way hat of the 65 and the little mouse nub of the 55. The pads are smooth and work as an axis. Personally I have them set up to trigger buttons. As for other differences. The Logitech X-56 seems to be better built than the older Madcats one, but time will tell. I have had mine for a year and it has been solid. I hope that helps

Now as a newish server owner, if my players do have to own it to play on the server running it. Can we easily disable it?

I think treating it the same way as any module is the answer. I fly the F/A-18C and F-14. My friend flies the F-14 and M2000C yet were not forced to only fly the 14, but instead we can fly any aircraft we own together. Do the same thing with that Carrier. The logical answer to me would be to lock the slots at the role select screen. Just like when my friend and I fly. I see his M2000 but I can not select it, and he sees my 18. The code is already there to lock the slots, so that seems like the logical answer to this issue, and the carrier select slot can't be that much different than an aircraft select slot. Just because it has more select-able roles doesn't change anything too because we already have Multicrew aircraft and those second slots are locked to people who don't own the aircraft. So limit the LSO, Boss, and other slots to people who own it. Just like every other module. Then make the module visible to everyone on the map, just like with other modules, but Still allow people to land on the carrier. While they are locked out of the stuff that makes it special, they should still be able to land on it and get basic features such as the auto LSO and Deck Crew walking about. I know it takes time and money to make those basic features, but to keep multiplayer from fracturing more, it could be worth biting the bullet and making those a core upgrade; Replacing / upgrading the Stennis. Then you just have to market the cool features such as controlling the boat itself. Which to be fair was the main selling point for me. Right now, I am in two closed multiplayer communities for DCS, one dedicated with about 60 or 70ish DCS users. The other one as a side community attached to a larger gaming community, a few hundred people in total from the full community, and about 25 or 30 who play DCS on the side. For the smaller community I run their private server. It is small but active, we fly a mix of everything. I have people who only fly Russian stuff, others who stick to navy, and some who only fly flaming cliffs. We even try to introduce people to DCS via the SU-25T. So in other words it is a new player friendly private server. The Navy pilots along with myself, about 8 of us, were excited for this new carrier, and planned on getting it, some like myself on day one, but since this news has come out it has been nothing but negative opinions on it. I personally since hearing this news will not be buying it, but also will not even host it on our server. It cuts out too many people and splits our already small group while making it harder to introduce new people to DCS. Even in the larger community which is a lot more hard core focused than the smaller one. The new carrier is being received mixed reactions. How does it affect current members? What about the air force pilots? How about members who can't afford it, and other questions. So even in this much more dedicated community the carrier is an iffy issue. I know they have to make money from it, and should not give out the full carrier for free, but if it splits part of the community. Then its bad for business all around. They might get more sales by making it compatible for Multiplayer than not. I personally was looking at buying at least one copy if not two depending on how it works for server hosts, and I expected to shell out at least 40 USD each copy for it or more, but the selling factor of being able to use it while my friends are flying on the same server not being an option has killed my excitement for the carrier, and I know I am not the only one, but I have hope that the right choice will be made. Also I like this idea. Could be a good way to generate money. Maybe if possible expand it to pilot uniforms and helmets too, or perhaps aircraft skins for notable real life pilots of those aircraft. Example Gypsy 207 and Gypsy 202. The two Tomcats who got A2A kills against Libya.

Found a possible Bug. During voice training TACAN Sierra Tango November is missing from the Command Phrase list. Drove me up a wall the last half an hour trying to figure out why that command doesn't work.

Same here, but I might have a work around. I found this bug last night while setting up keybinds on the MiG-19. I could keybind everything but Right Thrust. If I assigned an axis to right thrust it would cause this issue to pop up. Forcing a restart. I was able to bypass the issue by assigning one of my throttle axis to control both engines instead of left and right. Then I was able to add all the other keybinds and axis. I didn't see the issue pop up anywhere else but I still need to finish keybinding, so we will see. I hope this helps.