NineLine

Might be worth its own post in the wishlist section so it doesnt get easily missed Sorry to hear you are dissapointed, generally maps in DCS are not meant to be 1:1 to real world and only meant to give a look and feel that would be believeable, that said because its early access now is the time to give this feedback, especially if you have some photos or suggestions about improving the map, now is the time and one of the biggest reasons for Early Access. Make sure you get your feedback in the bugs or the wishlist section so the team sees it. As for the Cold War thing, well, I would guess that 100% of all missions, campaigns and such are not going to replicate any real world battle 100%. The idea of a Cold War gone hot is a very interesting 'what if' scenario for many, and I think it will be a lot of fun, especially as the plane offerings grow. Thanks!

I havent heard anything, I will chase it up again.

Hi, so I went ahead and tried Mission 10 on my own, after a proper start up, Datalink worked as expected. So I took your track and took control after alignment. I turned off D/L and realigned. After Alignment was complete, I turned D/L back on, and everything seemed fine. So, it seems like the error might have been caused by your alignment procedures. Please check and let me know. Thanks!

This is reported, thanks!

There are two crashes, one with DTC and one with the F/A=18C.dll, both are fixed internally. Thanks!

Hey WOPR, I tried this out on my own, and I do not think it's doing exactly that. So in my example, I created a new DTC, I saved it, then I imported on one I did earlier. When I imported my DTC, it did load in over the one I had just made, BUT If I did a save as, and save it as a different name than the one I made, I could switch between the two. If you just do a save then you would overwrite the one you had just made, it will also warn you that your are overwriting. SO some key steps. If you create a new DTC, before you import any more, make sure you save your work. When you do import a DTC, make sure you do a save as and save it with a unique name. Let me know if this covers this or if I missed what was happening here. Thanks!

Reported, thanks all.

As always, it's good to have tracks showing examples of issues you might still be seeing.

I believe this is known and fixed internally, but I will check with the team for sure, thanks!!!

This has been reported. Thanks!

Thanks, we will take a look.

Sorry, the track you submitted is corrupt. Can you send a new one? In the meantime, I will try and reproduce based on your description.

Will review and get back to you. Thanks!

Hey falcon_120, I have asked, and the team has stated that you can only set one threshold for each threat, and assign what AUTO program or NONE to dispense at that threshold. You cannot assign multiple thresholds/programs to a threat. Let me know if that answers your concerns, thanks!

Thanks, we will take a look.

Can you make a simple track for me in single player? Campaigns can have a lit of scripted stuff so for bug reporting a short sweet sp mission is best if possible. Thanks!

Because this is a thread for the Germany map, all, please stick to the topic please. If we have nothing left to talk about on this map I can close this thread. Thanks.

Quiet? Why do I have this migraine then?

Quick Start Guide - Data Transfer Cartridge (DTC) In this initial release, the DTC will enable you to create custom countermeasure programs and Comms presets for the DCS: F/A-18C and DCS: F-16C. In future updates, this will be expanded to include more mission planning data like navigation waypoints, targets, threats, datalinks, route points, weapon settings, and more. The functionality will also be extended to other aircraft such as DCS: AH-64D and DCS: A-10C II Tank Killer. Functionality on launch will allow you to create custom DTC cartridges for entire flights, or individual aircraft within the flight. The mission creator can allocate one or more of these cartridges to each aircraft, allowing the player to select at DTC most appropriate for the mission. Once created, the DTC can also be exported as a .dtc file, allowing you to create a personal collection that can be used in any mission you fly in either single player or multiplayer. Existing missions will not be impacted by the addition of DTC, as if there is no DTC assigned to the aircraft, the mission editor defaults will still apply. DTC files may be created and managed using the new DTC Manager in the mission editor, found in the EDIT menu, or from a DTC interface from within the simulation itself (discussed later in this document). When creating a DTC in the mission editor for the first time, select New from the File menu in the DTC Manager. From the File menu, you will also have the ability to Save, Delete, Import, Export, Rename, and return to Defaults. You will then see a pop-up window. Here you select the aircraft type you wish to create a DTC for and create a custom name for the cartridge. This name will be displayed in the DTC Load pages of the aircraft, and there may be limited space, so a shorter name is preferred. After clicking OK, the DTC file will be created. You will then be able to customize the settings. The DTC files are split into “Partitions”, and each partition contains different data types. These partitions may be individually uploaded from the DTC within the cockpit DTC Load pages. The partitions available on release are Threat Tables/Countermeasures (CMDS) and Communications (COMM), meaning that one or both of these partitions may be uploaded from the DTC within the cockpit by the player as they choose. As each DTC version will be unique for the corresponding aircraft, the DTC partitions (and the options within them) that are provided in the future will be notably different between aircraft types. Each partition is then subdivided by a series of tabs for each data type. For now, most of them are grayed-out (non-operational) until we finalize the general DTC design. Editing CMDS Settings and Threat Tables Each CMDS program may be edited to include Manual programs, Automatic programs, and Bypass programs. A delay may also be set between Automatic programs so that the avionics will wait before dispensing another program when the CMDS is set to AUTOMATIC mode. Each threat may be configured to trigger a specific CMDS program and the threshold at which that CMDS program is automatically dispensed. For example: if an SA-6 radar is detected by the RWR, the CMDS may be programmed to dispense CMDS program “AUTO 1” when the SA-6 radar is detected in TRACK mode, or it may programmed to dispense CMDS program “AUTO 3” when the SA-6 radar is detected in LAUNCH mode. This allows the mission creator to customize the defensive systems more thoroughly for what threats are expected to be encountered or how the player plans to defend themselves during the mission. You may wish to have unique DTCs based on the threat environment of a mission. The buttons along the top of the table allow each category of threats to be shown or hidden within the table itself to facilitate easier programming. Once you have completed your edits, use the File menu in the DTC editor to save the changes. Saving the DTC file saves it within the DCS mission (.miz) file, and it can then be applied to aircraft. Also in the File menu, you can Import and Export DTC files. This allows the possibility to create a DTC file and distribute amongst other players, and also to create a personal DTC for use in any mission you fly. To add a DTC to an aircraft, or aircraft group, select the Load menu, and then Load To Group in the DTC manager. A DTC file can only be loaded to Player or Client aircraft. They are not required for AI aircraft. All Aircraft of the correct type will be shown in the Load to group popup, and any saved DTC can be applied to individual aircraft, or a group. Once added, the DTC assigned to the aircraft is shown in the List DTC window. Multiple DTC files can be assigned to each aircraft, and there is a tick box to select the default - this will be the cartridge that is loaded into the cockpit at mission start. A DTC program can also be removed from the list by clicking Remove. If DTC are already saved within the mission, they can also be managed from the new “DTC” tab in the Airplane Group properties window on the right of the screen. This tab includes an option that permits the mission creator to enable the default DTC to be “pre-loaded” at mission start, which is particularly important for Air starts or Runway starts, but may also be used for Cold starts to represent an aircraft that has been pre-configured by crews for a rapid start-up and departure, such as quick response alert. This tab is only shown for Player or Client aircraft. DTC Management Prior to Flying a Mission There are two ways to manage DTC programs before flying a mission. For air or ground start aircraft, the DTC Manager can be accessed from the bottom-right of the briefing screen. For airstart aircraft, this is the only time you can select or edit a DTC whilst in the air. When on the ground at a friendly airbase, you are able to access the DTC Manager using the ground crew section of the communications menu. It is also possible to assign a keybind to show/hide DTC Interface, the default is RCTRL + RSHIFT + K Upon opening the DTC Manager in sim, you are able to Import and Export DTC files using the File menu at the top right of the interface. Importing a DTC allows you to import custom DTC settings into any mission. DTC files that have been assigned to your aircraft within the mission will be selectable from the Available Mission Files drop down menu. Select the DTC that you want to load into the aircraft from this list, and press the Load button. You also have the ability to edit the DTC at this point - simply edit the fields in the DTC partition as required. There is no need to save. However, you can then export this file if you wish to save for future missions. DTC Uploading from Within the Cockpit Each aircraft will have a realistic and unique procedure to load DTC data from within the cockpit. For the F/A-18C the procedure is as follows: On the SUPT main menu level, select MUMI using PB10. Once on the MUMI page, you will see the name of the DTC that is present within the DTC receptacle (which you have selected) displayed in the top centre of the page, and the different partitions of the DTC selectable with the push buttons displayed around the left, right and bottom of the display. On initial release, only COMM and ALR-67 are functional. More will be added in future updates. Selecting the COMM or ALR-67 PB will load the partition from the DTC. You can load any combination of partitions depending on your needs. There will be a delay of a few seconds before the selected partition is “boxed” whilst the data loads. For the F-16C, the procedure is as follows: Select the DTE format using OSB 8 on the top level MFD format menu. You will then be presented with the DTE page. In the centre is the name of the DTC that is present within the DTC receptacle. Selecting the “Load” option will load all available partitions. Alternatively, you can load individual partitions by selecting the appropriate option. On initial release, only MPD (Mission Planning Data) containing CMDS programs and COMM are functional. More will be added in future updates. Once loaded, the partition will be highlighted with white to signify it has loaded.

Not yet. Well, there is not anything I can share. I am reminding people as well. I did some research to see if it was indeed "easy" to rip ED models from memory and if it nullified our protection, and from what I can see, it is not that easy. That said, I am still pushing to get some of these things addressed.

We are in talks with a few of the manufacturers of the newest FFB devices now coming onto the market, we want to make sure the experience is everything it needs to be. While some modules have basic support, we want to improve it, especially for modules like Warbirds that will really be impacted by them.

I have requested this be adjusted some so that when using the slider in options, setting it to 1 has a much stronger reflection, I do see some, but it has to be at the right angle and in perfect conditions.

I was told today by our COO that: "We are aware of the pain creators have and we will think of the solution but it will take some time for us as it's a security issue and solution." So while it's pretty much what I said, BUT I think they are more actively looking at it currently.

I think it would be up to the 3rd Party if they wanted to protect them, I am not sure we would force them to protect them if they didn't want to, but I cannot say for sure. I will keep pushing, I was a livery painter back in the old days when I didn't know anything about no MV So I know the pain, and I know as models and liveries have become more complex its become more painful, I get it. But we just need to find a solution that does both. Its not lost on me that most times, things like this punishes the innocent harder than the guilty.

As I have said, requests are reported and I just said above what the team is busy with. 1. I assume so 2. The Model Viewer is still used for its original intended purpose, it was not made as a public livery tool. It still works for many tasks outside viewing our protected models 3. Anything is possible, but until our programmers can really dig into it, I can't say what that might look like, a MV lite? A built in MV in the game, I don't know. All I can do is ask and bug and see what we can get.