Leaderboard

WIP A-1 Skyraider's on SAR escort. seabat

So while the Admiral is getting all the ship fixes sorted he said it'd be ok to share my updated Normandie Frigate files. This update is more than just a fix for the "dancing missiles" and includes both the ASW and AAW variants of the FREMM "Aquitaine" class used by the French Navy. 3 ships and fixed/new missiles have been added. 2 ASW variants are D-650 Aquitaine and D-651 Normandie 2 AAW variants are D-656 Alsace and D-657 Lorraine ASW ships have either 16 Aster 15 (D-650) or 16 Aster 30NT (D-651) SAMs and 16 MdCN Land Attack Cruise missiles (760 nm range) AAW Ships have 16 Aster 30NT and Aster 30 Blk2 SAMs Both versions have 8 Exocet Anti Ship missiles as well. This is a update/patch so you will need the original mod. To install, remove original Normandie mod folder from your saved games folder and back it up. You will need to copy files from it. Copy the new mod folder to saved games. Then you will need to copy 4 files (ship edm files) from the orignal mods "Shapes" folder to the new mod's "Shapes" folder. D651_Normandie.edm D651_Normandie.lods.ship_wake D651_Normandie_collision.edm D651_Normandie (LODS File) Important. If you have any issues/conflict with this update message ME directly. Please to not bother the Admiral about this update or post issues in the thread. I will do my best to help with any issues. Note. Ship names in ME list are FS-DXXX and nation must be France D-651 update.zip

I would love to see this helicopter in the UK Assets pack

Well, I have one for you too.

Please fix this water. In the videos, we can see that the water in Afghanistan is green, yellow, blue and so on.. In DCS, on the map of Afghanistan, we see boring almost black water, as if the weather is cloudy all the time In DCS we see only this and Lake? By the way, there are still rivers and lakes of the right color in DCS, you see them when you fly at high altitude. Unfortunately this is only a part of the satellite photos that have become textures

When you hire a big game fishing heli charter, but realize you've bitten off more than you can chew! (...or is that the other way around?!) Just as well you brought along your trusty M60 machine gun, for just such cases! "We're going to need a bigger chopper"

Some 30 modules required updates for bugs that have improves (landing), still linger in DCS (dead/deallocated objects on events) and new features (dynamic player spawning). I'm hoping that I can publish an updated DML this week.

didnt... know that was an option

Relevant to note are the current limitations in infrared modelling also present. Missiles currently guide to model origin and not the engines in the case of infrared guided missiles. If you fire an AIM-9 at a Tu-95 it will guide towards the fuselage, not the engines. Also is the current two tier ir emissions system. Only two floating point values define the ir emissions for military power and reheat/afterburner, throttle setting has no further effect. I hope these are under consideration for being reworked in the future.

I am pleased to report that the engine response when performing AAR is now consistent again (at least for me). The update is very good (and very necessary, as I say, at least for me). Thank you all very much for your responses and comments. Regards.

This variant of the Phantom is not carrier capable and was not used to land on ships. Actual carrier capable variants had several changes and modifications, including on the gear, which also results in AoA changes that cant be translated onto the E directly. So you have to be careful when applying any IRL techniques for those other Phantoms onto our E, they might not work.

Click the D651 zip link at the bottom of that post and download from there Lovely work from yourself and Admiral, Beldin. Thank you. Ships work perfectly, look absolutely gorgeous and it’s a simple and straightforward install process. Thank you again

DASH stands for Differential Airspeed Hold. It is merely a tube with two actuators attached on either side that will extend or retract based on commanded speed via the cyclic or Flight Director. This will ensure the pilots do not have to hold forward cyclic to maintain forward speed, and vice versa. The LCT, or Longitudinal Cyclic Trim (Actuators) are what you're referring to. As speed increases, they extend on the FWD and AFT head, which will pitch both rotor systems forward, allowing the fuselage to remain level with the horizon regardless of speed. They retract at a hover and low speed to assist with hover attitude, and the drive to the GND position on the ground to assist with ground taxi.

I wonder if anyone here agrees with me (I even considered posting this as a bug) The beautiful low pitch sound of the flapping Chinook blades is already implemented (you can somewhat hear it if you zoom out far enough). In my opinion, it needs to be quite a lot louder though. In real life you can hear/feel this sound loudly from a very long distance and it's so distinct, that even the untrained ear can hear that a Chinook is approaching. When it gets closer, the high pitch turbine sound level eventually exceeds the low pitch sound of the blades slapping through the air and this is currently implemented quite well. Though from my experience seeing/hearing our Dutch Chinooks, I just think the distant "wokka wokka" sound needs to be louder. (simply turning up the main volume wouldn't be the same, as then the turbine and in cockpit sound would become deafening. I'm trying to say; either the turbine sound volume needs to be decreased, or the distant "wokka wokka" volume needs to be increased)

Starstrak OMG!!! STORMER

reproduced and reported thank you

This is a known issue I wasn't able to sort out before the patch shipped. Looking into it...

Thats because the AoA is different between the U.S.N and land based F-4s. Yes the tail hook is the same, but the AoA is different because the slats and airframe configuration are very different from the Naval versions. Between the gun in the nose (more weight= lower nose authority), the extra fuel tank in the tail (which balances the weight of the nose but changes the aircraft’s pitch behavior), and the wing slats vs the early Naval models’ blown boundry layer control leading edge slats , the F-4E is an aerodynamically different animal. Further, the landing gear is different as it’s engineered for land operations.

I can't make promises at this time. Rest assured we're aiming to make the DCS: F-16C FCR as realistic as possible.

Just to answer this question, the mission Operation Bactria (https://www.digitalcombatsimulator.com/en/files/201633/) would no longer work. I don't know if you are familiar with the mission but it aims to replicate realistic CAS in the A-10 using the Caucuses Mountains as a stand in for Afghanistan. There are four different flights of A-10s that get randomized taskings each flight also has a different AO (with some minor overlap) these flights are assigned to different countries (all using US skins though) and use the country trigger so that one groups actions don't overwrite what another group is doing, as would happen with a coalition specific trigger. Affecting country triggers is a side effect that I hadn't thought about until IronMike brought it up. Anyways thanks for updating the mod Rudel, it is something I will continue to use for myself until (if ever) there is a better option implemented I really like the idea of selected countries liveries are filtered at the top of the list.

Because the onspeed AoA is different, but the overall layout the same, the relative positions of the hook and the landing gear are different from the naval Phantom for a given AoA indication. Hence, if you touch down "on the donut", the hook will skip, since it'll be the same as if you had wrong AoA. You need to have the same "stance" as the naval Phantom, since that's what counts.

Daily MiG-29 Slovakian MiG-29AS 9.12A

The British Army... Otherwise agree it would be great to see this asset.

Asking for a date!

She don't like to be on the ship. Did my trials on flying that thing on speed to land on the carrier. The only time the hook grabbed was when I was fast and way to low (close to a ramp strike). With on speed it's bolter after bolter with the occasional broken main gear in the mix. Too bad, would be fun to pretend to be navy

Hey guys, it appears that there was a confusion and the above patch notes list some items that are actually not included in this particular patch. We will try to include them in a hotfix or make them available in the next patch instead. Sorry for the inconvenience and confusion caused by this. Items not included are: Inputs: Added Slow/Fast variants for Target Latitude/Longitude knobs (WSO). Inputs: Added UHF Repeater brightness control. Inputs: Added some missing TOGGLE and AXIS binds Inputs: Fixed Jester Scan Elevation (relative) binds being reversed. Inputs: Fixed afterburner detent option text and tooltip. Mission Editor: Support absolute pitch trim (iCommandPlaneTrimPitchAbs) Weapons: Added BDU-33 to inner wing pylons. Also, it appears that the introduction of the 2-stage trigger binds for the Flight Stick unintentionally broke the existing trigger-bind. Which means that you will likely have to map the trigger to your hardware again.

Problem is, what you see reported there is the overall usage of the cpu and not per core. 25% usage e.g. could be (most likely) a quarter of the cores running full bore whilst the rest is more or less idle. Same for the temp. In such a scenario the high loaded core or cores are probably hitting 90+ degree C. But the package temp is still reporting 62C. If you really want to monitor the health of your CPU, you need to monitor on per core basis.

This is odd - I thought it already contains that. Please be advised that the miz's name has changed to 'Sinai Tourist3' (note '3' at the end) so perhaps you have accidentally started the old version? You know that you have the updated version if Jerusalem has much, much more to show, and looks at least as busy as this: stupid null

А FFB на Чинуке скоро реализуют?

I'm currently working on RCAF D variants that flew in Afghanistan. should be done soon

Yes, it is Inviato dal mio SM-F731B utilizzando Tapatalk

Is this what you are looking for RWC? There are some minor issues with the gear but it does load in game Check here

"There is no such thing as a stupid question." On any processor it's the combination of high voltage, high amps and heat (they're usually correlated). But the big problem with 13th/14th gen has been (still is) the high voltage spikes. It's like quick intense "punches" of high voltage and heat, that hurts, then kills, these CPUs. The spikes happen mostly due to the single/dual core boost AND the high stock voltages. It goes over 1.5v all of a sudden when it boosts, some reports of it even going up to 1.6v ....when 1.4v+ was already bad. It happens instantly, so quickly and so many times. And your regular monitoring software usually won't detect it. You need an oscilloscope to see it, and that's exactly what Buildzoid already done on his videos to prove a point (see below his latest video, posted some hours ago). There is an ongoing theory, that the degradation happens because the Ring Bus shares the same rail with the P-Cores and E-Cores, then affected by the high stock voltages. The Ring Bus design of Intel is really not happy with high voltages (over 1.4v) and perhaps this could explain the processor slow suicide, cooking itself from there. But, again, just theory at this point (still to be proven). One thing is certain: to reach these high clocks and go against competitors, the stock voltages on Intel 13th, and again on 14th gen, had been (still are) raised to insane values. Now add the single/dual core boost 1.5v+ spikes to the equation. And transient spikes from loads changing. And VRMs response that can also cause spiking. And the thermal velocity boost limit that has been raised to 100ºC instead of 90ºC. It can not be good, the likelihood of something going wrong is definitely much higher. And that's why many locked the cores and undervolted their CPU from day one, or simply avoided them and went with either Intel 12th gen or AMD AM5. If you go to tech communities, there are plenty with undervolted 13th and 14th gen since these products launched, and no degradation problem. A pattern? Maybe, I don't know. I also don't know of any recent PC consumer grade processor that doesn't slowly degrade at 1.4v+.... and these go well beyond that, instantly, at stock settings. You can not let your processor hit that kind of voltage (1.50v or 1.55v !?! ), that's insanely high, even if temperatures seem ok. Even if with the new microcode, it can and will slowly degrade, and eventually it can and will fail ("kaput"). And why you should stop the single/dual core boost, easiest way being by sync'ing (locking) your P-Cores all at same max possible clock. And better if with the cpu core voltage (Vcore) manually adjusted to lower values, best if at 1.35v or below. One way to look at it is like some sort of undervolt that many also do on high-end GPUs (generally considered the best thing you can do to them). It prolongs its life, by lowering the voltage and temps. In this particular case however, and as described, it's (IMO) a necessity. Exactly. It is a problem if you're someone who knows very little about computers, and even worse if you don't know a thing about BIOS settings. People are not expected to buy a car and necessarily be mechanics. Countless people affected. I understand that Intel and motherboard manufacturers can not release BIOS with all-core "locked" clocks (no single/dual core boost), and adjusted cpu core voltages, because that would represent fundamental changes to a whole line of products that they marketed and sold to the public (a whole can of worms). But just like cars and motorcycles have had bad parts requiring "ad hoc" modifications (which no warranty solves), this is one of those rare cases when one should put hands to work and take care of his/herself (I know I would, and why I advocate it here). But then again, we go back to the initial point.... a problem if knowing very little about computers, and even worse if not knowing a thing about BIOS settings. *sigh*

Ok I'm happy to present the French Carrier Charles de Gaulle by the Cuesta brothers, Version 3.0 All asset of this mod belong to their original creators/owners; Source code by Cuesta brothers, Admiral189, Currenthill, cao990, Marroux, toan, and I'm sure I'm forgetting others. Thanks for all your work. Known issues (let's get these out of the way) You MUST have Admiral189's Normandie Frigate mod installed. (needed for Aster15 model) While a nice model there are a few issues I can not fix but they are minor. Model only has 2 gun mounts. It should be 8 or 3 depending on year/fit Model has 16 extra VLS tubes. It should be 4x8 cell. Model has 6x8 Minor glitches with rught side VLS hatch animations A few of the static deck crew may get run over by an aircraft. (causes no damage) Take off, taxi and landing script is (always will be) a WIP. Currently only the Rafale tested for ramp start/taxi. (F/A-18 will be added next) Catapult alignment is off for a few planes from certain spawn points. I will work to fix this. A new bug I've never noticed before. Anti ship missiles sometimes pass through the ship while others hit depending on the angle. LSO view is no longer working, I have no idea why Hopefully I did something stupid and changed my key command Wanting to keep the ship as close to "spec" as possible I ran into some issues with the way the model is configured. My initial attempts to remove/disable the extra missile tubes resulted in the hatches defaulting to their open position in game So that ship got a little weapons upgrade that can easily be ignored (in most cases) if total accuracy is your thing. The 16 extra tubes are loaded with the new MdCN land attack cruise missile. This keeps the hatches closed (if not fired) and if you do not give the ship a fire order in ME they should not fire. Note, If the CDG is in a group that is given a "fire at point order" they may fire. And I'm sure I've missed some other stuff so just PM with any issues or conflicts Now the specs Sensors Thales SMART-S MK2 (Air/Surface search) Range Air 155+ nm (250km) Range Surface 50+ nm (80km) Naval Arabel/SAAM target acquisition radar Range 62+ nm (100km) Datalink & Link4 for operation with US carriers (untested) SAM Systems 4 × 8 cell A-43 Sylver launchers 32 Aster 15 missiles, range 18+ nm (30-40km) 2 × 6 cell Sadral launchers 12 Mistral 3 short-range missiles 5+ nm (6-8km) 2 x8 cell A-70 Sylver launchers with MdCN Land Attack Missiles 760 nm (1,400 km) (see known issues) Guns (functional by still tweaking) 2 x 20 mm modèle F2 gun (orig gun code by cao990) Flight deck. Take off 16 total spawn points (2 runway, 14 ramp start) Landing, WIP Some planes CHARLES DE GAULLE 3.0.zip

Daily MiG-29 Russian 9.19

Aernov

Good night DCS...Love you!

It works now, 1. Enable Bob 2. Use your cyclic Stick Pushing stick forward - tells Bob to increase speed Pushing stick back - tells Bob to slow down Stick left - Tells bob to turn left Stick right - Tells Bob to turn right Collective Centre position - Tells bob to maintain Alt Collective up above centre- Tells Bob to increase alt Collective down below centre - Tells Bob to decrease Alt Now Bob won't fly above 160kts And if you give full collective up, the speed might come back as Bob won't exceed 100% torque

People complain about bad performance and ED’s response is “cannot reproduce”?

After going through the training tutorials multiple times, I'm currently studying the Chinook manual to understand the available systems. That's when this idea came to me... A training campaign for the Chinook, similar to "Iron Flag" for the A-10C, would be desirable. For example, a scenario where a Huey pilot transitions to the Chinook, just out of basic training, and is then trained at Nellis AFB for deployment in Afghanistan... Just a suggestion Cheers, Ghosty

Not simulated, but taken into account. Modern missiles have significantly greater resistance to countermeasures than older ones. You can compare AIM-9X vs AIM-9B in DCS. Sorry, but in reality there are no identical scenarios either. There are no such instructions - "throw up 6 flares against R-73, and it is guaranteed to miss". It may work, and it may not, since it depends on a lot of factors. The missile has a rejection of countermeasures mechanism. However, this also depends on the missile generation. I think you can easily fool the AIM-9B, but you will have to sweat with the 9X. Yes, you are right about that. We will think about it. Thanks for dialog!

Hmmm, I don't recall disabling those in the BIOS, if all I want is to lock cores and adjust Vcore (it's actually very simple). I only know how to do it in ASUS and MSI, because I usually only build systems with boards from these brands (ocasionally ASRock as well). With MSI Z690 and Z790 motherboards, I'd do it like this: "OC" on the left side of BIOS, to access the advanced settings. Then the following settings placed like this: P-Core Ratio Apply Mode ---- All Core P-Core Ratio ------------------ the max clock value applied for all P-Cores (f.ex, "55" for 5.5Ghz), as close as possible to the "Stock All Core" clock (depends on CPU). CPU Core Voltage Mode ------ Override (this changes the Vcore in use, from Auto to Manual mode) CPU Core Voltage ------------ 1.350 (the Vcore manually inserted value, my recommendation is that or lower, but up to you - that 1.350 corresponds to 1.35v) After any changes, save and reboot (F10 key in MSI as well, if I recall correctly). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Also, another thing that should always be looked in there just to be sure, in those Advanced settings of the BIOS: CPU SA Voltage ---- see what value is "greyed" there (i.e, what is currently used) At stock it's usually at 1.05v, and I never seen it over 1.30v with XMP loaded for whatever RAM. That should never, ever(!), be over 1.35v (the CPU degrades very quickly!). If for whatever reason you see that "CPU SA Voltage" at over 1.35v, imediately change the "CPU SA Voltage Mode" from Auto to Manual, and manually insert a lower voltage for it. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Then it's time to test and push your CPU to the limit and test stability. There are some that are good enough and don't take too much time.... - You have Cinebench R20 and R23 (continuous "CPU" runs are good to check voltages, temps, power, and have a final score to compare with each test). - You also have LinpackXtreme v1.15 (x64 executable, then select "stress test", 2GB, usually 10 or up to 15 runs for number of times, on all cores). Especially this last one is great to test stability - it's very demanding, if it passes and doesn't crash then (IMO) it won't crash with anything else. Whatever you do, always monitor your temperatures, voltages, package power (etc), pay attention to the CPU VCore with any changes you do (ideally under 1.35v). See if there's any single core boost (i.e, if any P-Core goes noticeably higher than the value you placed), or any spike on Vcore with it going over what you manually placed. CPU-Z is always reliable to show correctly the current real time VCore value, but it does not show any power (Watts) or temperatures, it's very limited for that. I'd strongly recommend latest HWINFO to monitor all those values (and so many more) when benchmarking and stress-testing (not really for gaming), it's an invaluable tool. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - If you're stress-testing with these new settings, with whatever aplication, and your system crashes, you can do different things (as you see best). You can decrease the P-Core Ratio (so, lower the max clock for all P-Cores) in 100Mhz steps (f.ex, if you used "55" for 5.5Ghz and that is not stable, decrease it to "54"). Try again, and so on. But you can also try different Load Line Calibration (aka LLC), to add V-droop. This keeps the CPU voltage from dropping (it won't affect power savings such as C-States). If going the latter route, then it's done this way in MSI Z690/Z790 boards: DigiALL Power (open this section) CPU Loadline Calibration Control - should be on Auto by default. Then change that to: Mode 5 ------------- this adds ~0.05v V-droop to the CPU voltage. or Mode 6 ------------- this adds ~0.09v V-droop to the CPU voltage. I wouldn't go neither lower or over those two for this exercise, but it's up to you. With the added V-droop you somewhat "stabilize" the voltage on the CPU. But it may run a little bit hotter (readjust the Vcore to a slightly lower value if necessary). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Another thing often used to help with stability for AVX applications (f.ex, console emulators, few odd games, some benchmark apps) is to use an AVX offset of minus one (-1). In MSI boards this is under CPU AVX Control, with the setting "CPU Ratio Offset When Running AVX". Anyway, if this all looks too complicated(?), then simply leave it as is, and ask for assistance somewhere else, friend, technician, etc.

With the massive Cockpit texture size, You GPU will run out of VRAM, especially in VR, and then it will start using system RAM, which are much slower, thus the bad FPS. Try to lower Textures to Medium, cause that will almost half Your VRAM usage with little graphics quality loss - in VR more or less unrecognizable.

I'm running at max resolution for my VR headset and they're barely readable, but yes too small.

It already is. Check out “Command Menu” in the controls.

Merci pour votre réponse, même si celle-ci ne me satisfait guère. Vos problèmes juridiques ou contractuels avec les sociétés sous-traitantes qui travaillent pour vous ne me concerne en rien. Vous protégez votre travail? Et vos clients dans tout ça? ça ne me parait pas être votre première préoccupation. Ce que je constate, c'est une viabilité aléatoire de vos produits. En effet, demain qui sera le prochain développeur avec qui vous aurez des griefs. Heatblur, Aerges ou un autre.? Ce que je vois , ce sont les conséquences qui se répercute sur les produits que j'ai achetés à vous Eagle Dynamics et non à l'un ou l'autre de vos développeurs tiers. J'estime que c'est à vous de faire le nécessaire afin que les produits que je vous ai payés restent fonctionnels. Vous pouvez me souhaiter le meilleur, maintenant que mon argent est sur le compte de votre société..Et en ce qui concerne ma confiance, vous l'avez définitivement perdue. Je vous laisse traduire..

Oh I need to check that then. The combination of MSAAx2 and quad view normally works brilliantly for me. *edit* I just noticed ED removed the “cannot reproduce” tag

You need to enable the system select knob to both on the trim panel. The startup tutorial doesn't mention this. I tried taking off and had the same issue. The taxi takeoff tutorial mentions it.