All Activity

Thanks ! I suppose 0.9.6 is the latest release?

So at last the Super arrived beatifully boxed and packaged Opened carefully examined everything and the DMAS speakers are missing. Notified PIMAX and --- After confirmation with the product line, we expect to reissue the DMAS headset to you at the beginning of October. Hopefully my 2 week Pimax play wont contain any limit of two weeks, as contractually its not fullfilled.

Type 3 in the WS declaration is AA. But in tests it will engage surface targets if it can. Type 6 is naval arty, Type 11 mixed iirc. The issue with this as I have found is that ED schemes are limiting. 5" were used as very poor barrage, 1 in 1000 rounds hit. I've spent hours on mods tuning this effect and it's not easily replicated. Worse, gun allocation is poor, there is some internal gun to target distribution that makes dual purpose weapons stupid. For example if close range to a high surface threat, in dual purpose it will use first come first served target allocation. It's going to be an issue when you see 18 inch guns and 5 inch guns together and 5 inches target the ship and 18 sits doing nothing.

Hi @Derbroomaster. So, my set up is that I have one touch screen onto which I display my swappable MFDs - so get pilots in the pilots station and CPGs when in the CPG station, and a standard 11.6 screen (non touch) that I have mounted a pair of tm cougars and display the CPG MFD only. On the 11.6 the CPGs don't swap - but obviously I can see them when sat in the pilots station, plus the pilots mfds on my touch. I have attached my lua - which might explain things - but I use a mixture of the helios export and a standard monitor set up - as things changed in DCS a few months ago so you don't necessarily need the patches. In addition - I have not installed patches for the pilots MFDs - so they keep the standard naming out of DCS (LEFT_MFCD & RIGHT_MFCD): I think I have been in this scenario before - but in essence you cannot display all 4 screens and expect them all to swap etc. Lua transcript below and attached - which I hope helps. _ = function(p) return p end name = _('Heliosa') description = 'Generated from Helios Profile CBI3' A_10C_2_CDU_SCREEN = { x = 3980, y = 62, width = 355, height = 276 } A_10C_2_RWR_SCREEN = { x = 5061, y = 302, width = 227, height = 227 } AH_64D_EUFD_PLT = { x = 4604, y = 15, width = 358, height = 177 } TEDAC = { x = 4578, y = 567, width = 440, height = 440 } Viewports = { Center = { x = -960, y = 0, width = 4800, height = 1080, aspect = 4800/1080, useAbsoluteFOV = false, FOV = 0.9428571428571429, useAbsoluteAnglesShift = false, viewDx = 0, viewDy = 0 } } --///////////////////////////////////// --A10C2 --///////////////////////////////////// function reconfigure_for_unit(unit_type) if unit_type == "A-10C_2" then LEFT_MFCD = { x = 5766; y = 148; width = 832; height = 832; } RIGHT_MFCD = { x = 6847; y = 148; width = 832; height = 832; } --///////////////////////////////////// --AH64D --///////////////////////////////////// elseif unit_type == "AH-64D_BLK_II" then AH_64D_LEFT_MFCD_CPG = { x = 5766; y = 148; width = 832; height = 832; } AH_64D_RIGHT_MFCD_CPG = { x = 6847; y = 148; width = 832; height = 832; } LEFT_MFCD = { x = 3921; y = 90; width = 487; height = 488; } RIGHT_MFCD = { x = 5181; y = 90; width = 487; height = 488; } --/////////////////////////////////////// --Flaming Cliffs --/////////////////////////////////////// else LEFT_MFCD = { x = 5766; y = 148; width = 832; height = 832; } RIGHT_MFCD = { x = 6847; y = 148; width = 832; height = 832; } end end UI = { x = 0, y = 0, width = 3840, height = 1080 } UIMainView = { x = 0, y = 0, width = 3840, height = 1080 } GU_MAIN_VIEWPORT = Viewports.Center HeliosFinal.lua

These units were done by M3L, the 3rd party developer of the F4U to support their module. Not ED

Although not explicitly stated in the news letter, we can infer from the forum position that this will be EDs module. That's important when looking at development time and features, what's coming is fairly predictable.

leider nix dabei, was ich such .... danke dir dennoch

Only Mother can love that Quasimodo...

Да было бы за что. Вчера проверил - летит всё как надо. Без захвата - ракета бегает за "3м крестиком". С захватом - летит, как мне показалось, чуть ниже крестика. Поэтому лучше брать повыше. Но это надо посидеть с этим, попрактиковаться.

Me too waiting impatiently a new tail rotor model, in fact I stopped Flying the Apache until they correct this awful behaviour!

Thank you. it really is

You padlocked an enemy, basically locks your vision to an enemy like you said. Just press F1 or Num5, that should unlock it again.

Version 1.1 Add Kneeboard Functions https://drive.google.com/file/d/1e0dZseXSM9cvlUA7wnYvI1qr9oovARPu/view?usp=drive_link

so i was playing the aerial gunnery in su27 .i accident slam my ipad on keyboard. A circle appears on enemy with crosshair inside of it and automatically make my vision follow the enemy. what mode is that

We have US paratroopers for ETO WWII and some from the VVD's LOMAC rusian modern, but we don't have paratrooper drop animations. I understand it's a very exaggerated effort, but it wouldn't be a bad idea to start seeing some movement by ED, especially with transports aircrafts capable of drop paratroopers. The problem with the ASC C-130J module is that it seems like we're going to have the ability to launch paratroops, but that "2020" US paratroop model is missing...and all the associated functionality, so I'm sensing that it's going to be in 2026.

First of all, map coordinates are geographic, not magnetic, so magnetic declination has nothing to do with coordinates being wrong. The magnetic heading of a runway changes, but the coordinates don't. I did a comparison of some landmarks in the mission editor and Google Earth, and they are all pretty much spot on (within a fraction of an arcsecond in most cases): Spandau Citadel, Berlin: Google Earth: N 52°32'27.69" E 13°12'45.51" Mission editor: N 52°32'27.63" E 13°12'46.49" Bridge near Hamburg Planetarium: Google Earth: N 53°35'28.36" E 10°01'29.58" Mission editor: N 53°35'28.35" E 10°01'30.16" Mainspitze, west of Frankfurt: Google Earth: N 49°59'37.29" E 8°17'38.38" Mission editor: N 49°59'36.82" E 8°17'38.94" Neues Rathaus, Hannover: Google Earth: N 52°22'01.74" E 9°44'14.37" Mission editor: N 52°22'01.98" E 9°44'14.67" Fulda airfield: Google Earth: N 50°32'31.32" E 9°38'20.91" Mission editor: N 50°32'33.14" E 9°38'19.03"

@slghtlystewpid Everything in scripts/MOZA directory. The main script is MOZA.lua, which calls the other scripts for some values. Are you sure it's not a config issue? Because I see in the RotorRPM script this :

@chipsdubbo I added trigger deactivating Snake 41 when player is RTB. This is some stupid DCS bug, but should be solved that way.

Hello Thanks for the reminder. I had completely forgotten about this important command. It works now. Thanks Raymond

OK, probably multiple things are going on here, so it's hard to say what exactly is wrong: Corsair-Complete-02.miz is clean, no baked-in views there. The other mission has Config dir inside it, it can be completely removed (Config/View overrides your views): This happens when the mission is "prepared" in the mission editor. That is Flight / Prepare Mission (Ctrl+M). Fly Mission alone does not do this and is safe to use. What happens with the Corsair in the clean mission, I have no idea. I didn't understand the story related to your screenshots of the View folder, not sure what happens when and what gets wrong. So, first step is to be always sure that the mission doesn't have baked-in views. With that, any other troubleshooting leads nowhere and just confuses you. Let's compare only clean missions. But with the "clean" mission, I have no idea what is going on.

This is now fixed internally.

the problem with renaming assets, is that any mission that used those is rendered obsolete. I’d prefer to keep the original name

It´s just that sometimes people tend to think, that the military gets everything they want/need at a heartbeat, whereas in reality they just go by commercially available products. If you have the insights, that those maps can easily be custom made, I won´t argue with you about it.

RX 6600 is not a great card, worse than the GTX 1080 I had. But it should be able to perform in 1080p, especially with lower to medium settings. What I can see is that your preload radius is waaayyy too high, this will kill your performance. Try the default of 60000, maybe even less. The maxed out CPU core could be that current bug, you will find solutions in another topic. Also, I'm not sure if your card even works with optiscaler and DLAA. Try MSAA 2x. The looks won't be that good, but performance should be OK.

those c-101 missions are from 6 years ago, so that vpc link points to an pbsolete Mod. try this updated version instead: