P5138

I just want to clarify, that when I said the 15 minutes felt too long, I meant that the 15 minutes felt closer to 20. I was sitting for much, much longer than I remember doing in the 1.2 version of the mission. I would have chalked it up to my getting better, but the shutdown trigger never went through either after at least five minutes of sitting, waiting for it.

I attempted the first mission in the BFT Campaign in 1.5, but it ended in failure: First, the 15 minutes for the startup sequence seemed too long, but I didn't have a stopwatch to check, then there were A10s in odd places on the taxiways, after that one of the fuel trucks drove through one of the Hogs, causing it to burst into flames and the pilot to eject (perfectly timed with the VO on the bustle of an airport), and then the mission ended with a U rating after I sat for 5 minutes waiting for the shutdown verification. Oh! And this happened while I was waiting: I don't know if it was 1.5 or a fluke.

I'm getting the same error in the Steam version. I'm DLing now in the standalone to see if it's common between installs.

This may be getting slightly off topic, but I've not seen the ARGS system before. Do you mean that it would replace the skin to an alternate file in the same livery folder based on the mission editor bort input or something like that? Or change the decal file to a different set of numbers? Is there more info on this somewhere?

I also got banned, as did everyone else in our channel.

Thanks! Whoops! I forgot to put in that my in game name is "Galahad". It would be a challenge to fly in both the Mi8 and UH1 at once.

As those slots just opened up, might I transfer to either one of the other helos (from the Mi8 ) if no one else takes them? I definitely am more confident in the Huey than I am in the Hip

I didn't catch this event until now. Is there room for a late sign-up for the final Mi-8 slot (or the Ka-50 slot that RightStuff had to leave in the post below, if that's more important)? In-game name: Galahad

On the squadron markings: Most of the Mustang's skins are created in a way that a mission creator can, at their discretion change the squadron code, plane designation, and the last three digits of the plane by changing a single parameter for the unit in the mission editor. The editor doesn't in any way restrict what the designer can put in the box, so it's possible to get incorrect markings. It also happens that the default input for the box is 10, so you'll often see a plane marked 010 (or 01, or 10) if no one bothered to change the value. There are specific skins which are fixed, like "Big Beautiful Doll" and others, that have the designations locked, but the rest of the skins are left to the mission designer to set. It's a 30 second fix if any are off, but it does require the mission creator to have noticed in the first place.

If Signup is still open, I'd like to join in: Galahad P-51D (w/ Wing Tanks and Full Fuel) or F-86 (w Wing Tanks) United States (EST) 2-4 hours I'm just wondering: I'm about to be getting to contacting the tower in my IRL training, would it be all right to use this as an opportunity to do some pattern work and practice approaches at the end of my first lap, just to get some more time interacting with the tower? Edit: Also would it be OK to do half laps with a cut north/south around Crimea? I'm just checking the charts and my range will not permit me a full lap with the Mustang or the Sabre.

The way I got around this, and granted this doesn't actually make it easier, is that I edited this part of the unit entry: Line [1] is group name (Enfield, Pontiec, etc.) Line [2] is group number Line [3] is unit number (max is 4) ["name"], as far as I can guess is the string that sets the way the ATC calls you. This method works to at least get the client to be in wingman spots like Colt 1-2. It won't make scripting easier, though, and it adds another few steps to the mission build process. It does, however, work perfectly well on the client side of things. Also, every client does get the full set of radio options as if there was an AI group behind him, so you do get some ability to use the radio system. It is only marred by the fact that you can't tell who says what. I also have tried to force non-normal callsigns into the section, like "Overlord11" or similar, but this totally breaks any communication that requires the name to be said. It would be great if we could get more than just the standard eight callsigns.

The code is placed in the default.lua, located in that folder, down near the bottom of the button entries. Paste it in a blank line directly above: I'm not sure that it has been fixed or not, but I noticed a problem with the code in the spoiler tag having line breaks added into random places by the forum because it's so long. Pasting the code with those line breaks causes the scheme to fail entirely. I've been meaning to replace the spoiler tag with just the code in a text file to avoid that glitch. Use the text in the attached file instead. I will be including this in the zipped control scheme file once I get around to updating the F-86 entry. add to default.lua

Quick Update: Since I just picked up the Ultimate Argument Campaign in the last Steam sale, I thought it was time to get a Su-27 card made up. The new card, along with its profile, has been added to the first post.

I just set the commands to a POV hat switch and they still only activate on the release of the button. I double checked the TARGET profile to make sure everything is normal there, and it is all set correctly.

I'm having an issue where the scan zone movement commands are only engaging when I release the key for the command, instead of allowing me to hold the key down and have it repeat. This is for commands: Scan Zone Left Scan Zone Right Scan Zone Up Scan Zone Down Radar Scan Zone Increase Radar Scan Zone Decrease Without being able to hold down the keys and have the Scan Zone continue to shift, it is very difficult for me to use my HOTAS effectively. I have experienced the issue when using the keyboard on its own as well as when programming the commands to DirectX inputs.

Thanks for the feedback. That is my server and mission, but it is also running my main laptop so I can't keep it up too often until I find a permanent solution or build a new server. For the time being, I'm putting the server up at around 1800 to 1900 EST, and pulling it down in the morning when I need to use my laptop again. The mission is still very WIP, so the server is up mainly to test the scheduled AI spawns and behavior as well as to run stress tests on the mission. For Teamspeak, I'm kinda unofficially and entirely by chance piggy-backing on the DoW teamspeak server for the times when I'm online (in the "Other DCS channel"). There isn't a dedicated Teamspeak for the server yet. That said, I must also echo dooom with the recommendation of the DoW server for ground pounding with the P-51D, unless you truly want to run with jets, then it's my server (when it's up) for the best experience... and that is a totally (un)biased opinion.

The cards as they are posted should be printed at a width of 109 to 110mm (~4.333 inches). I usually use Photoshop so that I can get the right size, but recently, I have been toying with putting bleeds onto the print so that I'd have a little leeway. Previous to that I was being extremely careful with a rotary cutter, then trimming the bottom corners against either the plastic covers or using one of the cards that came with the set. Even with all that care, I was often either cutting too small or leaving white around the edges forcing me to waste (expensive) photo stock on another attempt. On the MiG-15, as an experiment, I internally made versions with a 3mm bleed. This means each is now printed with a width of 115-116mm (~4.53 inches). It has alleviated the hassle of getting the cuts precisely at the edge of the ink, but it is not something I plan on retroactively adding into the older cards at this time unless it truly fixes the problem. I had also thought about creating a single pdf with both cards on a single page, but haven't really figured out a good way to do that and get it the right size yet. PDFs in theory would be better for this sort of thing: they can be set to a fixed size in the file for easier printing, but I want to get it right without wasting too much more paper in the process. In hindsight, I should have made these cards in inDesign or Illustrator instead of Photoshop. I've attached the versions of the MiG-15 cards with the bleed zone to this post. If something like this will make it easier to print out at the right size for the other cards, let me know. Otherwise, if a pdf version of the cards sounds better, I can experiment with a few ideas on creating them as pdfs. If neither of those solutions works for you, I can try to figure out something else that would work with programs built into Windows.

In response to requests for the profiles, I have added the majority of the DCS profiles I use for the cards to the OP. I've, for now, left off the F-86 and Mi8 profiles. I need to clarify some things on those two.

The 109 cards have been updated to fix the missing "t" and "f". Thanks for pointing those out.

Sorry for the long delay in getting these updates out. I have just posted updated versions of the F-86 and Fw-190D cards, as long as adding in new cards for the MiG-15. With the MiG's card, I will definitely need to add in the saved control schemes somehow. While my Russian isn't great, I will definitely admit that it will be hard for anyone not familiar with the language to translate the controls to the English equivalent for assignment. I am planning on eventually getting to the Su-27. I've been so engrossed by the WWII and Korean birds, recently, that getting back up in the modern stuff hasn't even been a consideration. I would love to see how that would turn out. With the small print on the charts and on a few of the buttons for my versions, I always figured an LCD would make the cards unreadable in places.

Are you looking for a Russian accent on these voice overs?

I was actually just going over the in-game luas for these. Expect some config files in the coming days; my PC required a full reinstall, so I will reprofiling everything anyway. Although I do use TARGET for the Warthog stick and Throttle, the MFD's are set through the in-game profiles. Many of the commands that are on the cards don't have default keybinds.

I added all the other vehicles currently in the sim except the Generic FC3 one I'm rearranging thanks to the Su-27.

Many. Thanks for those fixes. My German is limited to being able to say I can't speak German. I'll make the corrections and update them. Those last three are from the 109's panel, right?

I've been making cards for my Cougar MFDs for every plane in DCS:W/FC3 and wanted to share a couple here (mainly to ask if I got anything wrong on the German ones). If there is interest I'll upload the rest. I've made a set for every released ASM vehicle. To use: print the files out with a width of 109-110mm and cut to fit the MFD's card holder. I got the best results with semi-gloss photo paper. WWII Units: Bf-109K Saved DCS Control Profiles (zip): https://www.dropbox.com/s/kab6lrx347yk5il/Bf-109K4.zip?dl=0 Fw-190D Saved DCS Control Profiles (zip): https://www.dropbox.com/s/4dyt7agj8f0kdkq/Fw-190D9.zip?dl=0 P-51D Saved DCS Control Profiles (zip): https://www.dropbox.com/s/i9wtdcwkzvwgfec/P-51D.zip?dl=0 Helicopters: UH-1 Saved DCS Control Profiles (zip): https://www.dropbox.com/s/yz8nrron854vxxr/UH-1H.zip?dl=0 Ka-50 Saved DCS Control Profiles (zip): https://www.dropbox.com/s/xe47ftd97uc80oj/Ka-50.zip?dl=0 Mi-8 There are some issues with mapping buttons to the countermeasure system here, as far as I remember. Jets: F-86 Needs the following code added to the joystick input lua to function correctly: MiG-15bis Saved DCS Control Profiles (zip): https://www.dropbox.com/s/tu8wibqawilunfe/MiG-15bis.zip?dl=0 MiG-21bis Saved DCS Control Profiles (zip): https://www.dropbox.com/s/dzp1xeqiui42f7x/MiG-21bis.zip?dl=0 F-15 Only a Left MFD Card, Everything else is mapped to the HOTAS Saved DCS Control Profile (lua): https://www.dropbox.com/s/8p7kiqayrdiosjb/F-15C-MFD-L.diff.lua?dl=0 Su-27 Only a Left MFD Card, Everything else is mapped to the HOTAS Saved DCS Control Profile (lua): https://www.dropbox.com/s/jrwqqeiuobyushb/Su-27-MFD-L.diff.lua?dl=0 If anyone actually knows German and could tell me if I have anything completely wrong on the cards for the German planes, it would be great to know what to change to make the cards correct. Edit: Files moved to attachments so the post isn't ginormous. Edit 2: Corrected the Fw-190D and Bf-109 cards; added Helicopters and Jets. Edit 3: Fixed error in F-86 Cards Edit 4: Added Rocket Sight Adjustment Table (translated) to Mi-8 cards. Edit 5: Copied Radio Charts from Mig-21 cockpit onto the cards for easier reference. (They are not translated) Edit 6: Ka-50 Rocket Correction Table added to the corresponding cards. Edit 7: Long overdue, this one. Correctd Fw-190D circuit breaker typo; Revised F-86F's left card to be more useful (rockets and bomb controls are on the bottom row instead of the less-used gun select); MiG-15bis cards created. Edit 8: Revised the F-86 Right card to make caging and uncaging the sight easier to perform without looking by using the rocker in the corner. Edit 9: Bf-109K4 cards edited for typos Edit 10: Links to control profiles added to OP for most cards. Edit 11: Su-27 card added with control profile.