All Activity

après avoir tester plusieurs PA jais trouver que le SEM n'exploser pas avec le nez levé sur les mod HMAS Melbourne et le HMS invincible

8/12/2025 - Updated to version 1.8 ** Continued work the improve the cirrus cloud texture and shader - New and improved cirrus cloud textures - Cirrus clouds now change float direction over time - New beautiful seamless transitions between different sets of cirrus clouds - Cirrus looks better at all distances - Boosted star light for better night sky https://www.digitalcombatsimulator.com/en/files/3335023/

And the latest firmware for the Crystal OG is...? Pimay does not have a repository for Pimax Play or for the firmware. There is no changelog, not even a simple list for documentation purposes. Only scattered posts from employees or supporters from time to time. I like the VR glasses, but customer relations still need work.

I haven't updated yet but now I'm having trouble ending the mission rescue the handy wind. I get back to base and land but nothing prompts and then when I exit it doesn't say it's completed.

I believe what they wanted to say is that for a non-expert its generally better UX to have the aircraft shown as primary text and the radar name as secondary info than the other way around. Looking at it less from a challenge/practice perspective and more from a usability POV :)

Ah, that's something you can enable with the "Show Radar Description" hint when you hover over a radar with your cursor. It's something you can disable/enable for added difficulty.

To bring something new to this that only ED can do, I would want to see the routes and tasks that a player gave a unit via Combined arms, saved. This provides a complete RTS game, the ability to alter the battle, then save it, rather than watch all units sit still after saving because they no longer have their original route. Similarly, the routes and tasks that are provided by scripting, should be saved, i.e. what the unit is currently doing, not what it was told at the mission start. There's been so many methods to save unit positions over the years, so many people have had their take on this, including myself. Saving positions, is something. Saving the actual AI state (not even the scripting state, i'm not asking for that) is important because thats a fundamental requirement to restore the mission that we have never had. People don't really know how to ask for this because most of them don't understand about scripting, they just want to start where they left the game and cannot volcalize their needs because they wont know that the AI is just reusing the original mission file in the save game. If they move their carrier, save the game, they will be disappointed to find it sitting still with no route after loading. But even worse, if an AI commander is moving units, these all now stop and the battle is stationary. The request is another request for the ability to getTasks() from an AI controller. There is no API for actually asking for the current task of a AI unit. Some people might be surprised to learn this, others dont really care because they assume soemone can fix something like that, they don't know the scripting API. With this API, the unit position can be saved, as before and then the units route and task can be reliably given back to the AI so it can move to where it was last sent, providing a dynamic save, one that keeps the movement and orders should they have changed. This allows scripting to work freely. Scripters still need to pick up their units control at mission start, but they dont need to task any of the groups. Doing that takes a lot of work in collecting the "orders" in a remote database and tracking all the orders for reissue. I feel this has to be said because folks generally dont provide feedback at this level, so not providing this feedback allows anyone to assume that it wasnt wanted or needed, when it has been dearly wanted for many many years.

List of Military assets and bases during the conflicts in Angola, Rhodesia and Mozambique https://www.google.com/maps/d/u/0/viewer?mid=1FTZRYWTofj0FFufsgypuzPlauSuw3IOo&femb=1&ll=-15.810174298414127%2C18.88341560625002&z=7

Shouldn't have any trouble with them so long as you have the correct size selected & radar slaved to them. I haven't had trouble with them in quite some time

FAP-DAA Angolan Mig-23 SADF Troop with a R4

Cuban soldiers jumping from an Mi-8 helicopter landing in Angola, 1982. Soviet or Cuban Pilot photographed alongside an Angolan Air Force #MiG-21bis fighter jet, mid-1980s. FAPLA soldier with SAM installation 1980s Impala MkII firing a salvo of rockets

Export.lua, however I think if it’s not updating to the new version you may have two installations of Voice Attack? Or the wrong release? Yeah some missions maybe using scripts that interfere with the operation of Viacom, like work around DCS lua tables and provide their own. I won’t have a fix for this unfortunately.

Each ship has a different "size" they track just fine, But need to determine ship size. There is a chart somewhere out there. I will try to find it.

SADF Olifant tanks lined up before the start of Operation Hooper in 1988 Angolan SA-13 Strela-10 system in the bush FAPLA troops hitching a ride on a soviet-built BRDM SADF clearing SWAPO or FAPLA bunkers in the Border War circa 1980’s

Did you even read what I said man? UNDER 4000lbs. Not 6800 not 4500. UNDER 4000lbs. You really should be AIMING for 1200-1500lbs. If you are landing with that much fuel then you dont need tanks anyways. Try again please. And actually have a long flight that brings you under 4000lbs or just stay in burner. Again, 1200-1500 is preferred if you want to get full fuel. But you did just prove that it does vary depending on how much fuel you have so there is that lol. But just read what i wrote.

South African #Recce operators on the Quito river at a place called Mapupa, trying to recover an Angolan PT-76 during Operation Protea in 1981. They eventually destroyed it Victorino and Koos Stadler from 5 Recce Regiment

any news on this one?

Go to the controls, press on "Axis" at the bottom and then click on the axis that is affected by the issue, and then press on "adjust axis" or something like that. A new small window should appear where you can customize the axis, including curves and deadzones. If the movement of your pedals is only very small but constant, you should think about setting a very small deadzone.

deactivated core parking with regedit and still the same issue. Maybe less time to reactivate from block computer, but still the issue. Here the log and dxdiag DxDiag.txt dcs.log DSMC.log

Have you switched on the battery and inverter? Also, check fuel switches are correct. Cheers! Sent from my SM-G998B using Tapatalk

4 Recce Operator launching from sub

je viens de faire quelque teste avec la version actuel du SEM dabor jais appliqué se que eric a dit et mème comme ca je me suis aperçu que l'avion explose si je touche avant la zone des câbles, ensuite je suis aller atterrir le SEM sur un autre porte avion avec le nez levé et l'avion n'exploser jamais donc bizarrement ce problème d'explosion arrive seulement quand c'est une interaction Clem/SEM car le A4 ou le su-33 aucun problème sur le clem, ensuite je suis aller faire un essais un peu étrange je suis aller remettre la commande pour l’ascenseur ensuite avec le A4 je suis aller dans le hangar et jais décollé depuis le hangar (car quand l’ascenseur descend enfaite c'est tout le pont du PA qui descend donc c'est a utiliser seulement en solo) ensuite je suis aller tenter d'atterrir sur le clem avec le hangar abaissé et comme prévu le A4 est passer a travers le pont puisque le vrais pont physique est en bas , jais refait le mème teste avec le SEM qui normalement devrais passer a travers le pont, mais a ma grande surprise au moment ou le SEM a toucher la zone des câbles d’arrêt .. il a exploser , quelque chose entre le cul du Clem et la fin de la zone des câbles d’arrêt fait exploser le SEM quand il le touche je ne sais pas si c'est le modèle 3d des câbles ou autre chose mais il i a quelque chose , après que j'envoie ce message je vais refaire quelque teste et voir si c'est régulier et consistent je vous souhaite bonne chance et je suis impatient de découvrir la nouvelle version

as @razo+r attempted to point out to you, it takes more than lua code. I doubt it's a "DCS problem"; more likely the mod you are using doesn't have a 3d collision model including collision shells and collision lines that are matched to lua code that describes how the damage impacts the aircraft both in appearance and performance. I've seen models that contain very detailed damage modeling to others that have nothing. not all mods are equal in development effort and/or skill.

https://github.com/ThunderStruck-Simulations/F-23A-Spectre-Mod

I JUST got this stick (the WW ViperAce EX) but haven't yet installed the little attachment with extra hats and rumble activation. But, if I understand you correctly, you have the same stick and kept the force sensing options on in the Special menu, but put the dead zones to zero? Then used the regular pitch/roll axis tuning popup to add the deadzones back in? Do you know why this behaves differently? I've been flying this jet for a while but want to ensure I have the micro control to attempt AAR without crazy pitch changes...