Leaderboard

Thanks for the nice words everyone! I would also like to give a special thanks to all of you who have donated. You are the ones making all these assets possible. Every received dollar goes into models for new assets. I happily spend my time making assets, but I ask you for continued support since I'm a one man operation. Thanks! Edit: And here is a sneak peek of the next US Infantry release.

Project 11356R Admiral Grigorovich Frigate (Russia) version 1.0.0 released! Changelog Version 1.0.0 Release version

fixed in next update

Hi all, we have made the team aware, so far our auth server seems ok. We have had some routing issues outside of our control recently and I suspect that it is related. If I get any more news I will let you all know. thank you

I agree the VSN mod is no where near the level that Heatblur's F-4 will be but this is just objectively false. You can compare anything to anything else, comparisons do not have to be limited to whatever arbitrary categories you set. Here we have two simulated aircraft and two cars. Both items fit into broad categories and can in fact be compared. in fact you yourself just compared the corvette and fiat 500 by saying the Fiat is a better economy car while the Corvette is a better track car. That's a comparison.

fixed in next update

Done. Someone knows the reason that OAI painted three 767s ( N423AX, N441AX, N495AX ) in business jet like color scheme ?

@NineLine Indy here from VNAO CVW-7 (creators of the T-45C). We use the SC religiously everyday and are on edge for the same reasons @McKronenberg listed with this upcoming update. Our main concerns: Deck Crew Logic making our Carrier Quals more difficult to conduct (Day/Night) "Hold Position" bug JBDs getting stuck Not having access to Pri-Fly Colour PLATCAM Nice to haves: Player Controlled Weapons (e.g. Phalanx CIWS) Ability to walk around the entire ship without ejecting from the aircraft Ability to use Elevators Pushback tug Ready Room w/live TV's and radios Greenie Boards Eager to see the great work the team has done @NineLine, with bated breath.

WSO pickle button is only connected to air to ground release circuits. No Trigger in the backseat. You can use the HUD repeater to employ CDIP or AUTO with any bomb. The WSO cannot fire AAM's or the gun.

Maybe it is, maybe it isn't, obviously it's important to have a thread dedicated to it. This doesn't really change anything. A user could have a 10 TB disc. Once all 10 TB are filled, there is no more space. If removing 10 GB or liveries allows for a 10 GB install of a wanted program, the ability to remove the liveries was useful. This is disc size independent. It may be easy and affordable. Or it may not be. Again it's all individually dependent. I'd also say a livery manager would benefit the game regardless, so even if hard drives were free, there would still be a reason to create one. And still, there is value in a livery manager. I'd like to have one for the benefit of myself, other players, and DCS as a whole. The irony. The mountain of pure unfiltered irony.

This got bought first day, looked at, and put on the shelf. I finally pulled it up just because I was completely sick of deserts, and it's becoming my goto. Just enough big airfields, lots of room for boats, and if you space your AAR resources right you can go anywhere you want. Kind of like the real world, and I might tank off a KC-130 or -135 here, an S-3B there, and and Il-76 down there... It helps that I create my own missions, and I've done some formations on the west side at low/mid altitude and the views are stunning. For me, at least, it's been a pleasant surprise how much I enjoy the map. For my next trick I'll come up with some scenarios to fly. The nice thing is I completely ignore geopolitics. Good guys over here, targets over there...

It looks like Su-22M4 "early". We had several of them. They were without system for TV-guided weapons. here is one Russian

Yes, unless you choose a different directory for the save - which is possible. It is just the default offered directory. Just try it yourself: And then you see: This is otherwise not used by DCS at all. The configs managed by the game are all under Config/Input folder: This also includes your modifier setup for the plane, which is not otherwise savable. So, manually, you "back up" to InputUserProfiles, but it is all under Saved Games/<dcs-folder>, and you may wish to back it up somewhere else.

Given the feeling of DCS ww2 being a low level side project for ED, I understand why 3rd party developers don't want to get involved. Say someone made a SBD ok, cool awesome one of the coolest ww2 planes. But you can't use it as even 20 SBDs would suffer 100% casualties and not even get close to a Japanese carrier because of the insane gunnery of ships. (If we had a carrier.)

The CT uses the same radar scope as the C-200. The square scope is in the CR. I think the greater difference between the CT/CR and the M will be the stores (e.g. double bomb carriers on the inboards, iraqi 2200l tank) and lack of Corail CM stubs under the armpits:

fixed in next update

Yeah Flanker 2.5 - still my favourite for the planeset and the overall naval focus. But remember we had the MiG-29K in that, for which the weapon types in question were realistic. We don't have that anymore and as Silver_Dragon pointed out, they weren't realistic for the Su-33.

We did have exhaust hiders at some point but I might have deleted them by accident, Planned to maybe put them in the mission editor options vBBMF diplay with the old model in august remastered to 1080p

I bought this map on day one and I really enjoy it. I'd consider it Top 3 for me. Half my time in DCS is just for the fun of flying. I find other sims to be mushy. DCS feels the best for the sense of flight and the SA map gives you a huge scenic area for all kinds of flying. And I like the geography of it, it's cool to have Argentina and Chile in the sim. As far as missions go, I build my own and the map certainly has enough variety to allow for all kinds of scenarios.

@DishDoggie ^ They also don't have to create and code in internal structure (apart from places where it's visible from cockpit and from outside), damage model and weapon systems either. These things are a must, however, and take lots of development time in combat-oriented sims.

Hi, I agree with the thread creator. The first thing I do when I have reinstalled a module or after an update has been carried out: delete these liveries. A Livery Fictional Russia Air Force for the FA-18C? Or a Livery Fictional Royal Norwegian Air Force for the A-10C? Away with it.

It becomes a factor when 0 - negative Gs are held past a certain time. IRL, it's never a guarantee that it would happen. In DCS, it limits people from doing a bunch of silly things.

Im kind of worried with DCS incorporating he pacific. I am concerned we are going to see WW2 split in resources with that area, when we already seems (rightly or wrongly) to take second place to modern era weapons. Splitting the subgenre into two regions, when they have largely dissimilar weapons, to me doesnt make very much sense. I can remember Il2 making its somewhat abortive foray into the pacific. It was fun, but it arguably diluted much else they could have been doing, such as AI intercept radar they were working on. I would agree though, the best thing would be to expand Channel map to the east. If we got in Holland and maybe a bit of Germany, all the weapons we now have would be perfectly viable on the map for 1944/45. For me, whats really needed are more assets. If we had a Spitfire V and Me109F, and an AI Blenheim, we could cover the vast majority of the circus operations in 1941 and 1942. A glass nose A20 would allow us to cover the Ramrods all the way up to 1944. Building the flak defences, what ive really noticed we could do are a 37mm flak gun, and a small Wurzburg for gun laying. 105mm flak. For Normandy, im fairly amazed we have absolutely no coastwatcher radars, even though they were attached to every major gun battery along the coast. I dont think its the maps that are the issue. Some extra miles (which im sure isnt a cheap undertaking) would fix that relatively easily. Its the detail assets, thats the problem.

That's a beauty of an Aircraft i have all the Fixed Wing i can ever hope to Virtually Fly, but the Su-7 is one I'd have to add to my collection

Why would you test? It's intentionally modeled that way.

SA-3 had a few versions. SA-4 wasn't exported AFAIK, IDK if there are docs. But yes jesus we need an SA-7 and an actually accurately modeled SA-9.

And he compared two off the shelves cars. For the analogy to hold up, the Fiat would have to be modded. There are numerous YT vids of modded "lesser" cars leaving Ferraris and what not in the dust. And nobody in their right mind would compare a Corvette to a Ferrari? Or would they?

Only if it's not stored in Saved Games, which is not checked by IC.

It is named "Cannon 300-600m and missile lock/unlock button" in Mirage F1 controls binding. We have explained it in our changelogs as we implemented it after F1 inital release. We'll eventually add an explanation in our Flight Manual. This is en extract of the said changelog: Sidewinder missile will not perform SEAM (scan pattern) anymore as this mode was not implemented in the real F1. 'Cannon 600/Identification P' throttle button will now uncage Sidewinder missiles (except AIM-9B). If no target was detected at this moment, the seeker head will drift randomly following the background IR heat. The seeker will return to the boresight once the 'Cannon 600/Identification P' button is released. I.e. if a target is tracked, the button must be held pressed to keep the seeker on the target. AIM-9JULI launch delay was reduced to 0.4 seconds (AIM-9B/P/J still have 0.8 seconds). Magic 1 and 2 scan now is a 5 degrees wide rectangular pattern. Fixed Magic missile scan pattern. Sometimes the scan pattern size was excessively increased. Updated Magic missiles instantaneous seeker FOV. It is now 3.4 degrees wide. The two first points is probably what you are looking for. Replace the naming 'Cannon 600/Identification P' for 'Cannon 300-600m and missile lock/unlock button'.

Ok, then it should be fine with the next Release update (no dates).

Your system drive is full: Drive: C: Free Space: 0.2 GB Total Space: 237.9 GB File System: NTFS Model: Samsung SSD 850 EVO 250GB Drive: D: Free Space: 44.7 GB Total Space: 1907.7 GB File System: NTFS Model: Samsung 980 PRO with Heatsink 2TB Drive: E: Free Space: 31.3 GB Total Space: 953.9 GB File System: NTFS Model: Samsung SSD 970 EVO 1TB which means your pagefile cannot expand. Free up some space on your system drive (not only for the sake of DCS) and you should be good to go. (actually your two other drives are also almost full)

I'll just say that a clearly defined option for this really should satisfy 100% of people. I can see why people would be opposed to just letting any plane load anything in the regular menu: It makes it hard to determine what is historic in single player It prevents control of the features in MP (well not really since we added loadout restrictions, but then you'd have to figure out what is historic or not, etc) With a clearly labeled checkbox, everyone who wants a historic single player has it enforced. And I'd also say the checkbox should be disabled by default (ie all limits are in place without work on the part of users). This also means that MP servers are historic with weapons by default. Then anyone wanting to expand from there has the option to do so on their own in single player where no one else is effected or on their own MP server where joining is a consensual decision. I don't see the problem here, but if someone does have an issue maybe they can enlighten me. People can vote however, but if a no vote just comes down not wanting other people to have something (and I'm not making statements on how the vote options were interpreted here, if), I think that devalues that vote a bit.

Hi! That's the way to use NOSE. Just take an existing mission that could have some mixed sound problems, change the offending triggers with new NOSE ones, and that will solve the problems. Thanks for your words!

I don't get it. Unless you live there where your action is taking place (i.e. on one of the maps), whatever use is live weather to you? I prefer the ability to set the weather on-the-fly when starting the mission without having to go into Mission Editor. But live weather? Whatever for? Especially when it probably means IMC for 50% of the time. I fail to the the added value of that. Historical weather, maybe. Live? No priority for me.

In case of two external wing tanks: - Master Arm ON - Relevant pylon selected - Selective Jettison knob to STORES - Press JETT

Часть блоков комплекса УРВ.

So... How close will the F1M be to the French F1CT? I know they are different developments but the CT was also a later mod geared towards the air to ground, with one of the cannons replaced by a telemeter. As far as I remember, the round scope was also replaced by a more modern screen (that stayed on the right side of the dashboard) and a new panel was inserted below the HUD. I wonder to what extent it could be considered as a viable stand-in for the CT in scenarios such as French deployments in Africa or in Afghanistan (where they would be paired with the 2000D and its pod... that we don't have either).

Yep, an F-111 would add significant cool to the sim. Along with the F-104, a favourite since I was a kid.

I understand some people only want historical skins, but my Ka-50 came with an RCAF skin and I was happy to have it.

Unfortunately fixing prop governor still won't solve 3060 rpm dive limit which can be used in case prop governor loss due to battle damage and if engine revs up above 2800 rpm at that moment engine is lost which is not true.

I see I'm not alone in hoping that the Mirage III/V family will join DCS soon. Syria, Sinai and South Atlantic maps finally need their protagonists. It's long overdue.

Hi all I posted a reply to one of my own threads on the home cockpits forum regarding how to use an existing Capt Zeen Helios profile that works with DCS to produce your own one with just the stuff you need on it. It has dawned on me that being tucked away in that thread is not going to help many people simply because it is not an obvious place to be. As a result this is a copy of what is in there as I belongs in this thread. Essentially a working profile is used as a basis to create your own. For those who wish to know how I did it, it was surprisingly easy, if a little bit laborious. A big shout out to MadKreator37 over on the Helios Discord channel, without whose help I would still be struggling To summarise, the process is as follows. Firstly, go to your User/saved games/scripts folder and back up your copy of the Export.lua file (call it Exportbak.lua or something like that) Go to the Capt Zeen website and get one of Capt Zeen's predone profiles, in my case the A10C version, open it in the Helios editor and do the 'reset monitors' thing, setting everything on the main monitor. In my case, opening up the profile showed two monitors, 1 (main monitor) and a second one with a load of stuff on it. Resetting the monitors allows you to tell Helios to move the contents of monitor X to monitor Y. Your monitor setup will be different to mine, but you will almost certainly have a monitor that you view the main game on; make Helios move everything to that one. Do not open two instances of Helios editor as you need to work with everything in one instance of Helios Please note that when you do this initial work on a main panel called 'Interface status; you may see a load of errors generated. This is normal, and by expanding each section, if there are issues clicking on the little cogwheel setting icon will generally shop you what needs to be done automatically and by accepting it it will fix it for you, although there are some that are a bit more manual (for example where it says you must save the profile before it can be used) Once you have everything on that monitor, you need to decide what you want and on what monitor to set it on. In my case it was the RWR bezel, the entire HSI, the entire ASI and the entire ADI including the slip ball indicator. The problem is that if you try and look for these they may actually be on sub panels on the main display. On the right hand side you will see a list of all the components being shown in the Layers tab - except it isn't a full list. So, be careful not to delete stuff without knowing what it is. The other thing that may occur is that the images all come up as red boxes with black crosses through them. That is because the images being used by the profile are in a sub folder you downloaded with the profile in it. To correct this you need to copy the image files and subfolders from the download location into the Helios installation images folder. When you save the copy of the profile you are making it should automatically show the correct images. Now you have to start deleting things. If you click on the item in the right hand Layers list it will highlight it on the monitor screen (if you double click on the monitor in the top left preview screen it will open in the main panel - be sure to click on the actual number in the middle of the preview as if you don't sometimes it won't open the screen). When you can see that the highlighted item is something you don't need / want, you can delete it. Continue that process to declutter as much as possible. Eventually you will get to a point where you have a lot less that includes the ones you want, and they may actually be in a sub layer (for instance mine were in a sub-layer called 'main panel'. On the main screen you can double click on these and they will appear in a new screen and all the sub parts will be listed in the Layers tab to the right. Depending on the instrument, clicking on it will open yet another with the sub components of that instrument. Unfortunately that doesn't seem to be very consistent, but it doesn't seem to matter. So assuming you now have a condensed list with just the items you want (possibly with some unwanted extras) now it is time to put the desired instruments in their correct location. To do this you will copy and paste, using either ctrl-c and ctrl-v or the edit-copy and edit-paste commands. Select say the HSI from the layer list; you will see it highlighted on the main screen. Copy it, then open up the screen you want to put it on, and paste it. Doing this has now copied all the subcomponents and layers, and more importantly all the bindings that let it interact with the DCS info. Follow the same procedure for all the desired items, placing a copy of each on the appropriate monitor. Obviously save as you go in case of mistakes or issues. When saving, you may get some other errors generated in the 'interface status' tab, just repeat the actions you did earlier and it should all come good. Some errors might remain but are ones that don't affect the workings. Now you should start the profile using the Helios Control app, and hopefully it will start without errors. If there are any problems it generally will be easy to address, as there is information given. Hopefully it will start OK and so what you will see are two sets of instruments, the original ones on the main screen, and the new ones on the screens you chose. Start DCS and if all went well, your instruments should all show the game generated data, and work with it. If that is the case, congrats, you can move on the next stage. If not you will need to verify the Interface status, and that the Saved Games Export.lua is referencing Helios, which should have automatically happened when you went through the initial Interface Setup error correction Now you have to go through the laborious reiterative process of stopping the profile, dragging the individual instruments to the correct size and positions, then restarting the profile to check it. Bear in mind that while the instruments will snap to the borders, this can easily be overridden by simply typing in the desired position in the top right panel. A lot of mine are set at like -5 from the top so the top of the instrument is off the top of the monitor, so that it displays in the exact location to match my laser cut bezel. The same goes for the left position, height and width. You will have to keep starting the profile, checking it for position and aspect ratio and then correcting as necessary. Once all the positions are correct restart DCS to check that it all works, save it one more time and then save as another filename so that the working one is still there in case you have issues. Once you have done that, go back to the original instruments that are in the wrong place and delete them, leaving only the instruments that you want, and save. If all went well, you new should have a fully working Helios profile. One other thing that I had to do once I was finished with Helios was to ensure that any viewports I had created were correctly aligned with the Helios instruments. For example, the RWR symbols were way off center, being too far to the left and down. In the Monitor Setup.lua file I then had to adjust the start position (x, y) and once I had that correct I had to make sure that the height and width of the viewport matched the Helios version. Again, this is a reiterative process, where you have to change the numbers, see how it looks, and then change it again until you are happy. I would say it took me most of an afternoon to get it all right, but the finished setup looks really great. The thing is that with patience you can do it One last point - you may have to copy the DCS Bios line (something like dofile blah blah DCS Bios) from the Export.lua you backed up at the beginning in order to get DCS Bios working with it. I hope that this helps, I am not an expert on Helios but this worked reasonably easily for me Cheers Les

Thanks for all the work you have put into these mods. I love them. Just wanted to check in. We haven't heard from you in awhile. Hope you are doing Okay.

Yes. What's your point? If you improve an imperfection, it won't be as imperfect there, will it? Then as far as I'm concerned, we're done here, there's no argument to be had. But in that case, why are you seemingly arguing against something if you are by your own admission fine with it being incorporated? But, for however many times I've said it, having a good, high capacity storage drive (which I have), doesn't justify why I should store files I don't want, use or need, that can be deleted with little to no consequences (less so in multiplayer, but definitely so in single player). I don't know why people keep bringing up this point when it's irrelevant in that it doesn't justify, nor does it follow at all that you should store unnecessary files you don't want or need, because they're small and storage is cheap. Which doesn't justify keeping it full of slings and arrows. Things simply being the way that they are, doesn't justify keeping them that way, does it? And if it doesn't justify keeping things the way that they are (especially things that can be improved), then what point are you trying to make here? You're just saying a whole lot of nothing. Worse, is that this logic is completely useless, if everybody had this mindset nothing would get done, nothing would be improved. No bugs would be fixed, no new features would ever be developed. Is that what you want?

Hello!Would be cool to see SS-21 Scarab A (Tochka) for ukraine,very want see that rocket

All but the 2nd option is something that already happens with the integrity checker as it is, if it's not a problem already, it won't be so with the liveries, especially if its default behaviour remains as it is now (i.e liveries unenforced). "Yes we can!" Followed by a complete non-answer, that's been addressed over and over again, only to be totally ignored. Shocking. And why does that mean that none of the imperfections should be improved? Oh, so it's fine to have a system for campaigns (which, some of those are only a few gigabytes and a very small percentage of the install size), but not for liveries? I mean, clearly if we can remove stuff using manager that's also small and that's not an issue in the slightest and nobody wants to have it removed, then it being small isn't an argument against a livery manager then, isn't it? So we can discard both arguments as being irrelevant nonsense whose conclusion doesn't even follow, can't we? And it would take up less space if there was a way of stopping it from redownloading things you don't need, want or use. Even if I've got loads of space, why should I store files (even if they're only small files) that I don't need, want or use?

Ignore it. If you are VFR, look out the window and navigate via pilotage. If you are not VFR, you are flying radio nav, in which case just follow the needle. It only really matters when IFR trying to do precise dead reckoning and the maps are so small in DCS that it doesn't really matter.

Putting some life back into the thread. DCS really needs a designated bomber and I’d love to see the mighty F-111c be created. In service from Vietnam war till retired by RAAF in 2010. Cmon, what an epic aircraft!!!

At least Compressor stall seems ti be simulated - what to complain about ? When doing silly things - expect silly behaviour.