All Activity

heres that.

With recent options being added to the advanced waypoint options. It would be nice to add the ability to control the external Position/Formation/Nav lights and strobe modes. For example being able to PID different flights by light modes. This would be great for mission makers in all areas(campaign makers, single player, multiplayer that use AI). I understand some aircraft have different external light modes but here are some examples down below. - Advanced (Waypoint Actions) > Set Option > Position Lights > Bright, Dim, Off - Advanced (Waypoint Actions) > Set Option > Formation Lights > Off / On, Steady / Flash. Maybe light brightness 1 being low, 3 being high. - Advanced (Waypoint Actions) > Set Option > Strobe > Off / On. Depending on aircraft select modes for example the F-16 Modes 1-4, A-C. OR The F/A-18 having bright, dim, off.

Not against Linux myself, however the steps to get this setup are gonna be beyond a lot of users. Until such time as DCS and other vendors provide their software for peripherals, VR runtimes, and any other supporting software all decide and support one Linux distro (or one common enough that it will work on multiple distros) then some of these points are moot. A lot of software vendors will not port their software to Linux. I'd certainly look at Linux, but right now all those other items are a complete blocker. This is not just a DCS issue.

Another interesting stumble. For a single digit Number? Put a Letter before and after it. ie. 'a7a' Gives you a centered '7', on both the fuselage and gear doors. Bowie

F4U DevGru - Tail Hook Inoperative w/ Gear Up Neither keybind nor mouse (no activation 'green' symbol) Works fine with both w/ the gear down. Bowie

I updated my post, with new info.

DCS in VR is the only reason I'm still running Windows on the flight simming rig. I'd love to switch that over to linux........

Yes, that's correct! A 2015 F-35A would be a Block 2B which has all the limitations that I mentioned above. Resuming, basically only AMRAAMs and GBU-31s could be employed autonomously by a F-35 Block 2B aircraft and these weapons could only be carried internally which for example means no AIM-9X Sidewinders either as these are carried externally in the F-35. Even the Block 3i which was basically a Block 2B with stability and mission effectiveness enhancements was only completed and started testing in 2016 (and as such, after 2015). Despite being a F-35 fan and as such, DCS F-35A being the module that I'm anticipating the most for DCS, if it isn't a Block 3F then I agree with you that I won't buy it (it will be a hard pass for me either). And not making a Block 3F because of any lack of documentation would be a lame excuse since in reality all the diferences between a Block 2B/3i and Block 3F are all software-wise which allows the usage of the Gun, the ability to carry more types of weapons such as the GBU-49 and GBU-39 SDB, it gives of course the self-lasing capability, adds the ability to carry external weapons (such as AIM-9X, GBU-12, GBU-49, GBU-31, etc...), expands the F-35 flight rules which allows for example the F-35A with Block 3F to be capable to attain 9G's. Resuming, these are all capabilities that a pilot wouldn't notice by simply looking at the cockpit display as otherwise it looks exactly the same as a Block 2B/3i would look.

looks like a jst ph or sh 5 pin connector. There are several places online that sell these. Installing is very simple and some even come with a tool. JST, PHR Female Connector Housing, 2mm Pitch, 5 Way, 1 Row. Got a pic of the other side.

F2 can use damocles, it’s just by the time it was ready the F3 was available

I just dont know what kind of connector this is. I took it to an electronics repair place and they couldnt source a cable for me. I dont think this one is going to be hard to find, but Ive no idea about this stuff. This is why Im asking, I dont know what kind of cable I need. I just know its a 4 pin USB 2.0 cable with a 5th wire thats shielding.

Thanks a lot, @Silver_Dragon

Hi guys.iav started the weapons training for the mi8.is there a way.were you can have the instructor talk to you instead off reading txt all the time.?.thx

Из большого числа знакомых пилотов мало кто играет в авиационные игры. В WT вообще не слышал, чтоб кто-то играл. Потому что на полет это меньше всего похоже, наверное. В этом отличие, одно из. Если послушать, чего хочет сообщество DCS, то эмоциональных запросов самых разных наберется «вагон и маленькая тележка». А когда хотелки воплощаются в жизнь, многие забывают порадоваться тому, чего сами и хотели. Мне немного непонятен сам запрос на баланс. В конфликтах то реальных самолеты очень сильно разных возрастов встречались и могут встретиться. Тот же Фантом всё ещё летает, вроде как. Ну и сбивайте его для поднятия настроения, просите «начальников серверов» регулировать доступные типы и оружие, хотя они и так это делают. И бегущая строка оповещения о воздушной обстановке и другие условные штуки имитации хорошего управления авиацией. Да и потом, побеждать на более сложном для освоения аэроплане разве не вдвойне приятнее? Модуль молодой, будет дорабатываться долго и активно. Результативность его во всем будет ещё расти, как и будет стираться точная граница между ростом навыков вирпила на нем и улучшением самого модуля. Не говоря уже о том, что значительную часть сообщества нагибучесть самолёта в онлайне, как и сам онлайн, мало интересует в принципе.

It's in there. I haven't looked closely yet, but RAF Northolt is there.

Nice work.

FWIW, you got a couple more errors on that LOG, make sure it's not a mod (or a problematic module) creating the problem: Line 205: ERROR EDCORE (528): Drivers errors while mounting coremods/aircraft/f-15e/liveries/f-15ese/usaf 17th ws af90 low vis clean.zip: Line 206: ERROR EDCORE (528): ZipDriver: Failed to open zip archive coremods/aircraft/f-15e/liveries/f-15ese/usaf 17th ws af90 low vis clean.zip. Line 223: INFO DX11BACKEND (544): DX11Renderer initialization (w:2560 h:1440 fullscrn:0 vsync:0 adapter:0 monitor:0 shaderErrors:1) Line 239 to 258: ERROR DX11BACKEND (544): Shader "/shaders/ParticleSystem2/groundPuffComp.fx" failed to compile. Reason: /shaders/ParticleSystem2/groundPuffComp.fx:65:1: W4300: Redefinition of LIGHTING_DECAY. /shaders/ParticleSystem2/groundPuffComp.fx:66:1: W4300: Redefinition of LIGHTING_DECAY_SECOND. /shaders/ParticleSystem2/groundPuffComp.fx:67:1: W4300: Redefinition of LIGHTING_FLAGS. /shaders/ParticleSystem2/groundPuffComp.fx:68:1: W4300: Redefinition of LIGHTING_SHADOW_PARTICLES_COUNT. /shaders/ParticleSystem2/groundPuffComp.fx:69:1: W4300: Redefinition of LIGHTING_WORLD_OFFSET. ParticleSystem2/common/clusterLighting.hlsl:77:31: W4300: Redefinition of ComputeLighting. ParticleSystem2/common/clusterLighting.hlsl:78:39: W4300: Redefinition of ComputeLightingInternal. ParticleSystem2/common/clusterLighting.hlsl:79:36: W4300: Redefinition of GetParticleLightInfo. ParticleSystem2/common/clusterLighting.hlsl:80:42: W4300: Redefinition of GetShadowParticleLightInfo. /shaders/ParticleSystem2/groundPuffComp.fx:75:1: W4300: Redefinition of LIGHTING_DECAY. /shaders/ParticleSystem2/groundPuffComp.fx:76:1: W4300: Redefinition of LIGHTING_DECAY_SECOND. /shaders/ParticleSystem2/groundPuffComp.fx:77:1: W4300: Redefinition of LIGHTING_FLAGS. /shaders/ParticleSystem2/groundPuffComp.fx:78:1: W4300: Redefinition of LIGHTING_WORLD_OFFSET. /shaders/ParticleSystem2/groundPuffComp.fx:79:1: W4300: Redefinition of LIGHTING_PARTICLE_SHADOW_GET_FUNC. ParticleSystem2/common/clusterLighting.hlsl:77:31: W4300: Redefinition of ComputeLighting. ParticleSystem2/common/clusterLighting.hlsl:78:39: W4300: Redefinition of ComputeLightingInternal. ParticleSystem2/common/clusterLighting.hlsl:79:36: W4300: Redefinition of GetParticleLightInfo. ParticleSystem2/common/clusterLighting.hlsl:80:42: W4300: Redefinition of GetShadowParticleLightInfo. /shaders/ParticleSystem2/groundPuffComp.fx:902:20: E5017: Aborting due to not yet implemented feature: Non-direct structured resource store.

I think I must have found a way to obtain the data of groups or units. But when I wanted to write to a new file, there was a problem. io.open() couldn't be used. I really don't understand. I won't do it anymore. This has already achieved my goal. Thank you for your help! Thank you!

It's the Steam edition.

Is your copy of DCS a native Steam build, or did you install the stand alone version of DCS using steam?

You're not supposed to use NVGs like that. Full screen NVG mods should disable the blurring of close objects like the cockpit. That setup might be a nightmare to play with. With blurring, you interact with the cockpit by looking out of the NGV goggle frame, not inside it. Try to disable that blurring on the mod you're using, there is no down scaling to 180p (I realize it was a jab at DCS) or whatever. Have a look at this one: https://www.digitalcombatsimulator.com/en/files/3345896/ There are many options to chose with reduced blurring and with mask, which is the one I use. The blurring is still present on those. ''NOTE: To customise the effect yourself, open each file in a text editor and search for the keyword "Tune." Every "Tune" comment explains what the adjacent variable controls.'' There are directions on how to change the depth of field effect.

Unless that's how a JHMCS projects night vision, which I doubt. That's not how night vision (nvg, nods, whatever you want to call it) looks. I.e a full screen effect. But yes I agree night vision needs a rework. Funny enough if you look at the pilot 3d model in the cockpit from the F4 view, the pilots have a blue glow from the new models.

Hi. I've got the latest release 2.9.14 lua and looking into it. Sinai terrain's last three new airport / air bases may not be added. "Khalkhalah Air Base" "King Feisal Air Base" "Taba International Airport"

2 is ok but 3 is about space, not good against dcs low alt pseudo ballistic missiles. but i will see. need to restore all s*it