Bogey Jammer

Prove yourself that it has been mounted then… because I can post as many picture of 2000C without it as you want which proves nothing, you just need one to prove your point. Anyway it is pointless to install the D2M if the aircraft is going to be a new variant or replaced by the Rafale. The only way to get hope is to check the Egyptian Mirages, I don't see any other 2000C equivalent around now. Don't play dumb. Sorry if I can't speak german to make this clear for you but even if you can mount the D2M on a 2000C, toggle the D2M switch on, it will never work because the internal hardware needs to be upgraded, wich was never done on a 2000C ok??? R-27 have been adapted on some India's Mirage 2000 so will you ask RAZBAM to implement them in the same fashion as the D2M ? You don't like it? don't read it then :P leave the ones who still have arguments left to continue the discussion.

No it's not like the Mig-21 AG missile. It's more like if Leatherneck decides to install the R-77 on the MiG-21bis because the bison version does. Not the same impact on gameplay, we are talking about PvP here not PvE. Even though the intention of implementation of the DDM is initially for strikers players. I'll definitely use the DDM for AA combat every time to kick your ass online if you like it :D

Of course Absolutely not Yes, but nobody knows if it was mounted for other air forces' Mirages 2000 yet. So ATM it's seems purely fictional for me.

You just said the fatal may word… Don't you think this matter has raised enough controversy ? So perhaps it's time to investigate a little bit ? Please mate you will say that after you actually test the thing in combat. I'm serious, aircrafts in dogfight have to maneuver (seriously?) and missiles fired by other aircrafts that the Mirage is not chasing can happen to be in the dead center of the detection zone. So stop trolling me :mad: Just buy some popcorn and wait for solid feedback. I don't care using the DDM, but if features of this nature creates unnecessary community conflicts, the raison d'être of DCS is dead.

Maybe you're asking too much from the AI. You should apply simple paths and tasks because it obviously tries to constantly adapt its behavior to the situation, thus conflicting with direct orders. Anyway like humans, AI is in this case programmed to not see where exactly are the SA-3 launchers and still executes the mission with the consequent safety margin.

That's crazy, this is definitely a game changer… At least this module will sell better for people willing to avoid being disadvantaged :D because the M-2000 is now the most advanced aircraft in DCS. Can't wait to see the reactions after a few MP games ;) I repost this, because I think that is an incredibly overlooked fact : So the DDM on the 2000C may be 100% fictional after all:megalol:

Most of people voted F-104… Are we condemned to fly 'murrican eternally ? :cry:

Yeah but McDonnell Douglas doesn't agree with you. You still can ask Han Solo to install a hyperdrive, that's a few values to modify with a text editor…

I just wondered if we can have smart views mode for watching tracks à la DID F-22. The principle would be an automation of switching cameras and units selections based of the events of the combat, because most of the time I don't know exactly the track's contents and there is no rewind feature to review missed events. Moreover, in DID's F-22 there were some camera traveling and some smooth movements that increased dramatically the action. It also got some filters to limit the viewing to units concerned. I have never seen better since then. Smart views like cycling through units to present the situation, going to the missile view that is going to be launched, then watch the target trying to evade it, select shoulder and target's tail cameras in dogfights, etc… :D

Isn't that planned for the future aircraft carrier modules ?

More than one time recently I could fire an IR missile to the back of AI units without being detected… Seriously more tests have to be performed to determinate the AI's situation awareness effectiveness.

Excellent teaser

Thanks for the appreciation. Everything would be nice to add. I actually need that sort of frequency remainder dynamically generated. However there are some choices to make, like the use of the room available to add more information in the table without scaling down the font too aggressively. There is another problem. We virtual pilots have the tendency to put waypoints on beacons to fly a route directly above them to get the simplest navigation management as possible. It's OK for crowded heavy VFR civilian traffic but on the battlefield I'd place a SAM near each these overused beacons by the enemy :devil:. Real pilots use the clock and anemometer for off-road navigation. Beacons are used to materialize FIX points with the help of radials. That is advanced flight route planning and it is impossible for a script to guess that sort of pilot thinking and write down the corresponding directions. Instead, I will make another scripted page, more oriented to the mission itself, with a resume of all possible frequencies that are to be used in the mission's area, accorded to the aircraft's radio equipment and presets, + a script listing all the aircraft's radio presets and the corresponding beacon/station. This plus beacon graphic representation would help the pilot to pick the frequency according to the way they intended to follow.

Done, see the first post. Thanks to MikeMikeJuliet for the pertinent suggestions. Time to go to bed

Hmm… That is indeed a very interesting equipment, as well as every thing else in the Spanish military, but playing as Spanish is… well, quite uncomfortable for me because there hasn't been significant involvements of Spain besides NATO coalitions, or high tension periods that affected eastern "western" Europe, for getting scenario interest. Spain lacks military charisma from an outsider like me, although I really like this aircraft and appreciate the quality of this army. I can be ignorant about the Spanish army history, so I'd like to know what kind of plausible scenarios would be imagined to play with this module with the current theater asset, AND without the NATO/US background.

Cool, looks like it's already loved :D But, bad news, I can't make it work for multiplayer missions yet. Unlike singleplayer missions, the DCS's way of putting multiplayer temporary mission data is not as straightforward and clear. I still can manage to load the data but I'm not able to know what flight the player chooses. There is still hope, a solution may be found by extensive reverse engineering. I'd also like to make my script compatible with the Nevada TTR map that I don't own. So I ask if anybody can send me via PM a temporary singleplayer mission using the map (or simply give me the value for the ["theatre"] keyword inside the mission file). This mission file is generated at: C:\Users\*username*\AppData\Local\Temp\DCS\Mission and is just called "mission" without extension. However it only exists while the mission is running, so get a copy before you exit the mission. I'd also like to check the Beacons.lua file for the Nevada map (if it exists). That file should be located at: C:\Program Files\Eagle Dynamics\DCS World\Mods\terrains\*nevadasubfolder*\ Also, communicate me that *nevadasubfolder* name because my script indeed needs it to read the Beacons.lua file… Thx in advance

I'm almost ready to release my flight plan page. But if you still want to discuss about it, there is the dedicated thread: https://forums.eagle.ru/showthread.php?t=175186 ;)

Hello all :D Introducing my semi-dynamically generated flight plan page: It is a lua script generating the player's flight plan (and related information) when the page is loaded. It remains static during the mission's run, that's why I specify it as semi-dynamic. It allows customization of the displayed data (units, annotations, table, sizes, colors, margins…). So it is possible to duplicate the script file with different settings to display pages with different contents, allowing the dilution of annotations that can very easily overlap when waypoints are close together. The script is attached to this post along some examples of calling files (read the installation procedure to learn what I'm talking about). The current version is 1.1 CHANGELOG: V1.1: -- Added MPH speed unit availability -- Added distances between waypoints calculation -- Added SHOW_SEGMENT_SPEED settings -- Added SHOW_SEGMENT_DISTANCE settings -- Slight enhancement of waypoints' annotations visibility -- Added basic collision management for overlapping segment annotations V1.0: -- Initial release WARNING: The script doesn't work in multiplayer mode since this mode uses a different way to store mission's temporary data. Moreover, the player's chosen flight is not specified in this data and is to be determined by a yet unknown method. Since I don't own the Nevada TTR terrain, I've never tested the script for this terrain and I've currently blindly wrote compatibility code. Let me know how its going on this map, Consider this script as a WIP. Significant enhancements can come from public's ideas so feel free to suggest here. INSTALLATION INSTRUCTIONS: Reminder of the DCS's custom kneeboard system If you don't know yet, DCS allows user to display customized pages into the in-game kneeboard, sorted by aircraft. Usually these pages are static pictures, but the system can execute lua code for dynamic content. All the custom files are located here: %USERPROFILE%\Saved Games\DCS\Kneeboard (Just type it in the windows' explorer address bar to go there) Now there should be directories named after all the aircrafts you can fly in DCS (if missing, create them, the names must match their counterparts in Program Files/DCS World/Mods/aircraft except for Flaming Cliffs aircrafts that are seperated in the kneeboard directory…) Then in each of these aircraft directories, you have to put your custom kneeboard pages. Philosophy of the BJ's flight plan page file layout Instead of duplicate the same whole script in every aircraft folder, we will utilize the ultra convenient feature of lua consisting to have just ONE main script file and call it from each aircraft with just two lines of code. This way it will be much easier to update the script (just one file to replace), and to setup the displayed pages because it will require to write the only settings that differ from the default ones stored in the main file. BUT, that is still too cumbersome for me, so I prepared a more extreme organization. Let's say you have 50 western aircraft modules and 80 eastern aircraft modules (DCS in 2-3 weeks :lol:) Will you replace the same calling file with respecting settings 130 times if you mistaken a single setting ? hell no. So these settings can also shared in another intermediate file, resulting of a single line of code in each aircraft for calling these shared settings files. Just like Cascading Style Sheet. There is still need to create 130 lua files for this single line of code :doh:, but they will never be touched again :thumbup: However some aircrafts may have specific settings (like the MiG-21bis with its kneeboard exotic dimensions), so a caller file with its own settings must be created for each of these aircrafts. The procedure Inside the kneeboard folder, create a new folder called Shared, then put the BJ's SD flight plan page.lua file inside it (this file is attached to this post) Open this file with your favorite text editor (no text processor), and look for the localization parameters: These localization parameters tell the script to display the various mission's texts in the specified language if the mission maker created them. Modify these two parameters according to your needs: I purposely let these settings to detect anyone who haven't RTFM :devil: (sauf s'ils parlent déjà Français…) In the future you may have to change some of these default settings in the same way. They are common to all aircrafts and overridden by the ones provided by the calling scripts. Let's create a calling file for the MiG-21bis. Create a new file inside the MIG-21bis folder with .lua extension and any name. Edit the file and copy/paste the following lines: dofile(lfs.writedir().."Kneeboard/Shared/BJ's SD flight plan page.lua") BJSDFPP{ UNIT_ALTITUDE="km", UNIT_SPEED="kmh", SIZE_WP_NUMBER=0.002, SIZE_WP_DISCRATIO=15, SIZE_ANNOTATIONS=0.002, SIZE_TABLE_TEXT=0.0025, SIZE_TABLE_CELLRATIO=19, SHOW_SEGMENT_ANNOTATIONS=false, SHOW_WP_ETA=false, SHOW_WP_NAME=false, SHOW_BEACONS=false, SHOW_SEGMENT_SHORTTHRESHOLD=0.33, SHOW_SEGMENT_HIDETHRESHOLD=0.17, }(or download run BJSDFPP MiG-21 table.lua attached to this post) This will call the main script and override the specified parameters to fit the flight plan inside the non-standard dimensions of the MiG-21bis' kneeboard. Note that the text size unit is unrelated to the page's unit system. So we have to configure all these parameters to show the flight plan page properly without any glitches. I personally don't use any third-party kneeboard modifying application, so that issue may apply to anybody altered the default kneeboard's dimensions as well. Now we will create a shared intermediate calling file. Inside the Shared directory, create a new file named run BJSDFPP shared west general.lua. Edit the file and copy/paste the following lines: dofile(lfs.writedir().."Kneeboard/Shared/BJ's SD flight plan page.lua") BJSDFPP{ UNIT_ALTITUDE="kft", UNIT_SPEED="kn", }(or download run BJSDFPP shared west general.lua attached to this post) This is the common calling script that will be called by the 50 western aircrafts you will own sooner or later… And, inside one of the western aircraft, create a new file with .lua extension and with any name you want. Edit this file and copy/paste the following line: dofile(lfs.writedir().."Kneeboard/Shared/run BJSDFPP shared west general.lua")(or download run BJSDFPP west general.lua attached to this post) Then copy this file into any other aircraft that must use the same shared settings. You can place many calling files as you wish inside one aircraft folder, there will be as many kneeboard pages generated. I hope this was not too hard, but life ain't easy… run BJSDFPP MiG-21 table.lua run BJSDFPP shared west general.lua run BJSDFPP shared east general.lua run BJSDFPP west general.lua run BJSDFPP east general.lua BJ's SD flight plan page.lua

Please, LN, feed the hamster every day…

About the MiG-25, there are no spare parts made anymore since ages. It is tactically obsolete and inferior in every way. The MiG-31 is still protected and will ever be. It is so strategically sensitive that it has never been sold outside Russia, or passed to former soviet states. We'll never see it as a DCS module. Another wishlist thread that will go to waste… And to balance the game, the best enemy for a F-14 is the anti-ship cruise missile.

Like this ? DCS: King Kong

It is perhaps better to not tell anything rather than scheduling feedback releases that never happen. Otherwise topics and behaviors like this would not exist.

Quite good news for me, thanks for letting me know, but like you said the post is outdated and the progress is slow, damn slow. It still is the topic of the most annoying still unrepaired stuff, even though it is said that ED is working on things mentioned for… years if not more than a decade. ;)

This is not a bug but I've got sick of lock-on era then already Lo-res 3D models of AI units, especially some aircrafts I want to put the most in my missions (Su-22, F-4, Su-34). I think about it every time I launch DCS. Look at my avatar, don't you recognize a pilot face ? I also add the zoom out effect in cockpit at mission start.

We perfectly agree on this. No. Like I said, The G-meter shows an acceleration value along the normal of the wing plan, in other words, it is the same forces as what are applied on the pilot's ass. If the aircraft is diving at -90° or climbing at +90°, it shows 0G, the pilot feels nothing in his ass, but they are rather felt in the back or straps. Dr_Arrow's illustration shows perfectly what it is about. During uniform movement, the G-meter can show 1G only if the aircraft is flying perfectly horizontally. It was the case both after bomb release (indeed) AND before.