Ithronwise

In point track mode targeting pods are able to follow a moving ground target automatically and of course to illuminate it with the laser, otherwise you would have a hard time to hit it with a laser-guided maverick or hellfire. The same technique should work with LGB's. The bomb follows the laser and as long as the target is in range it will be hit.

Does Rev.2 work with 2.7.18 or only with 2.8?

Unfortunately Germany will not buy the Super Hornet/Growler anymore. Instead they will buy F-35A as nuke carrier and a modified two-seater EF-2000 as electronic warfare platform (which has to be developed first).

I think the problem is that the program that Eight Ball has used for a batch conversion didn't ask him for a compression level and just used a default one. In paint.net you can choose which compression level do you want if you save a file as dds, but as far as I know there is no batch function in paint.net.

I have played a little Sherlock Holmes and compared the folders file by file. The missing file in the Texture folder is uncriticical because in the original folder the OV10_PILOTE file is existing twice, first as dds and second as png (whyever). In the Cockpit\texture folder there are two files which aren't exist in the folder of crazyeddie: OV10_cpt_viseur_bille_NRM.png OV10_cpt_viseur_reglage_NRM.png I will change them into dds files and copy them to the other dds files. Then I will test whether the issue is still there. EDIT: Ok that's it. Issue solved. EDIT 2: Here you can download the missing dds files: Missing files of Cockpit_texture_Folder.zip You have to copy them into OV-10A Bronco\Cockpit\texture

I have found a small issue (see picture): I have compared the number of texture files in the folders of the unchanged mod with the number in the folders by crazyeddie and it seems that there are some files are missing. Original Texture folder: 150 files Crazyeddies Texture folder: 149 files Original Cockpit\texture folder: 290 files Crazyeddies Cockpit\texture folder: 288 files Because of the large number of files it is hard to say which texture is missing.

I have just tested the dds files by crazyeddie. The readability is much better now and seems to be the same as with the original png files. The loading times and performance are still awesome as they already were with the dds files by Eight Ball. Now I use the cockpit textures and other textures by crazyeddie and a mix of dds-based liveries by Eight Ball and crazyeddie. Great work, guys and many thanks to you both. With crazyeddies DDS files:

Yeah, I think it has something to do with the compression level of the dds files.

@Eight Ball With the dds files by Eight Ball the loading time and the performance are much better (no stuttering and fps drops anymore when I look around in the cockpit). Unfortunately the readability of the cockpit instruments is much worser than with the original png files. It seems as if they wouldn't be "anti-aliased": With original PNG files: With Eight Balls DDS files:

Is there an update? Because this bug becomes very plesky. As long as ED isn't able to create dynamic campaigns, a lot of us want to build our own complex missions and campaings. If we have to check whether the chosen skins are still there every time we reload a mission in the Mission Editor (and this for dozens of units in the worst case), then this is a waste of time and very annoying. Every minute we have to deal with such a bug we don't fly, and if we aren't able to fly we are losing our motivation and if we are losing our motivation we will stop buying modules. Something to think about.

I am deeply sorry for you. In this case you are right, it would be necessary to have an option for an alternative nose wheel steering.

If you buy the modules via PayPal or credit card, the price will be automatically converted to EUR when the amount is debited from your bank account, depending on the current exchange rate.

Did you have set deadzones for the toe brakes of the Logitech Rudders in the A-4E-C control settings? I have deadzones of 25 on both toe brakes. This prevents the Skyhawk brakes from reacting to the slightest movement of the feet, what would resulting in unwanted moves to the left or to the right. So, you have to hit the brakes short and hard to steer the plane. This is much easier than trying to steer the aircraft by gently kicking the toe brakes.

The only way to avoid this would be to deactivate the cargo as soon it is dropped on the carrier deck and then activcate another one identical cargo unit which is linked to the carrier ( but I am not sure whether static cargo can be linked to a ship). Somewhere exists a script named simpleStatics.lua. I have it in my Scripts folder and it works very well (I used it in some complex missions) but I cannot find it anymore here in the forum or in the internet. With this you can activate and deactivate static units as you wish.

Sorry, I meant "Triggered Waypoint Action" (as I wrote I tried from my memory). Now I am at home and I tested your mission. I understand your problem and tried to solve it . But the closest I get is this what you can see attached. Unfortunately the Mission Editor is very limited and the DCS AI is artifical unintelligent. I am afraid the only or at least simpliest solution is to set the carrier speed to zero. Or you give tools like M.O.O.S.E a try. Cargo Test modified.miz

You don't need to specify the cargo zone as unloading zone, therefore you have the Advanced Waypoint Action to unhook the cargo (e.g. "cargo 1"). And Trigger 1 works, because it doesn't say any more as: If "Cargo Chopper" is in the moving zone "cargo zone" of the zone unit "carrier" then set "flag 1" to On. Trigger 2 says: If Flag 1 is true then push AI Task unload/unhook "cargo 1" (the Advanced Waypoint Action you set) Trigger 3 says: If "cargo 1" is unhooked in zone "cargo zone" then send message to all: "test" To be sure that the helo is flying to the carrier you could set a waypoint task "Follow" (e.g. for a waypoint somewhere near the carrier route) and set its values that the helo hovers directly over the carrier with synchronized speed.

I am not at home at the moment, so I will try from my memory. First you have to create an Advanced Waypoint Action for unit Cargo Chopper to unload/unhook the cargo. Then you have to create the following triggers: Trigger 1: Type: ONCE Conditions: UNIT INSIDE MOVING ZONE = Unit: Cargo Chopper Zone: cargo zone Zone unit: carrier Action: FLAG ON = Flag: 1 Trigger 2: Type: ONCE Conditions: FLAG IS TRUE = Flag: 1 Action: AI TASK PUSH = Action: unload/unhook cargo Trigger 3: Type: ONCE Conditions: CARGO UNHOOKED IN ZONE = Zone: cargo zone Cargo unit: cargo Action: MESSAGE TO ALL = Message: Test The problem is, I am not sure how long the helo needs to drop the cargo. If he takes too long time, then he drops the cargo into the sea because the carrier moves on.

You have to set the Cargo Chopper as unit to activate the trigger. Translated in a syntax: If "Cargo Chopper" is inside the moving zone "cargo zone" of the zone unit "carrier" then start action "message to all: test".

Hi Flappie, I tested it and can confirm, the issue is gone. No more black flickering spots in the cockpit with SSAO = On. (But I leave it OFF now, because I didn't miss anything without it in the last months and with it ON I have some light performance hits). Thanks to you and the ED team.

There are many pictures and videos on the internet showing that the USN Super Bugs (and Growlers) regularly use the outer pylons. All kinds of weapons can be carried there that can also be carried on the two inner pylons (AMRAAMs, Sidewinders, guided and unguided bombs, HARMS and so on). Five minutes google search:

I also have Logitech rudder pedals, but I have no trouble steering the A-4 precisely. I control the little bird by short, alternating kicks to the left and right toe brakes. If you try to stand on the left or right toe brake to force the plane in the direction you want to go, you will lose that battle.

Hi pet333r, thank you for you reply. I downloaded the latest scripts-extended.zip from github and copied the contained folders to the Saved Games\DCS Folder. The MFD's are working much better now (no more connection problems). However, the map is working only sporadically and it seems it depends on the used plane. In the F-16 the map shows the position and the heading, speed and altitude information of the plane very reliably. In the Hornet or the Harrier it only works sometimes, mostly not. All over features (UFC, right consoles and so on) are working fine. With some testing I have found the cause of this behavior. It is Windows-related and has to do with the kind how I am starting DCS. I have a folder on my desktop which contains the shortcuts of all of my games. When I open it and click on the DCS shortcut the DCS window runs in the foreground, then goes into the background (behind the opened games shortcut folder), then starts in fullscreen and as soon the DCS menu screen is showing (and the DCS Util.exe is starting) Windows minimizes DCS to the task bar. This behavior is only showing with the installed Script Configurator for your app. But if I am starting DCS without opening the games shortcut folder (e.g. by a DCS shortcut directly in the task bar) or I close the games shortcut folder right after DCS is starting, DCS stays maximized and in fullscreen the whole time with the DCS Util.exe running. So, obviously it is not a problem of your program but one of many Windows "features". Best regards, Ithronwise

Du könntest DCS auf 60 fps limitieren. Entweder über die autoexec.cfg im Ordner Saved Games\DCS\Config (options.graphics.maxfps = 60) oder über die Nvidia-Settings (dort müsste es auch einen fps limiter geben), dann solltest Du auch ohne VSync keine Streifen mehr haben, da die max. Framerate des Spiels mit der max. Bildwiederholfrequenz Deines Monitors überein stimmt und DCS bzw. die GraKa nicht mehr versucht dem Monitor höhere Bildraten zu senden als dieser darstellen kann. VSync macht ja auch nix weiter als die max. Framerate des Spiels an die max. Bildwiederholfrequenz des Monitors anzupassen. Grundsätzlich würde ich Dir allerdings raten (sofern es Dein Budget erlaubt), einen ordentlichen Gaming-Monitor mit höhere Bildwiederholfrequenz und G-Sync zu kaufen. Der würde defintiv besser zu Deiner PC-Konfiguration passen.

Sowohl seine CPU als auch das Mainboard sind mehr als ausreichend dimensioniert (guck Dir die Spezifikationen an). Und PCI-Express 8x zu 16x machen keinen so großen Unterschied (dürfte im einstelligen Prozentbereich liegen), jedenfalls wäre das kein Grund für eine derart bescheidene Framerate, erst recht nicht in Full-HD. Ich hab "nur" ne RX 6700XT, die ebenfalls "nur" auf 8x läuft wegen zweier NVMe-SSD's, und habe mit fast allen DCS-Grafiksettings auf Max bzw. Hoch und WQHD-Auflösung selbst über sehr GPU-lastigen Bereichen (Tiefflug über Guam z.B.) mindestens 40 fps, ansonsten 60 (die FPS habe ich auf 60 limitiert, ohne Limitierung so um die 90 fps). Ich denke, das Hauptproblem liegt wohl im Vsync. Da er das aber nicht deaktivieren möchte, wird es schwierig, das Problem zu lösen. Treiberprobleme, Probleme mit Overclocking, Hardware-Inkompatibilitäten und komische Windows-Settings (Thema Spielmodus, XBox Game Bar oder Vollbildoptimierung z.B.) können natürlich zusätzlich eine Rolle spielen.

It's a very helpful app (thank you for this work) but I am missing the Marianas map. Is there any plan to implement it in the near future?