All Activity

I'd certainly fancy a Westland Lynx (surely there's a place in DCS for the world's "fastest" helo)(also, DCS could do with some more non-US western modules) But I'd definitely also buy the CH-53 if it were available. With the Hook and Herc, DCS is focussing more and more on cargo hauling in their sim, so the Stallion would be a great addition in that respect

https://youtu.be/3Q3C-riVXkU?si=EpHKoGxH7jG0kEAq

Забыл спросить кстати, а чем отличаются лазерно-лучевое командное и полуактивное наведение на отраженный сигнал?

there definitely are problems in your results. can you try another just IPv4? ping -4 cdn.digitalcombatsimulator.com (-4 forces ping to only IPv4) here are my results. there should be no timeouts. Pinging 1231349722.rsc.cdn77.org [109.61.91.195] with 32 bytes of data: Reply from 109.61.91.195: bytes=32 time=10ms TTL=57 Reply from 109.61.91.195: bytes=32 time=10ms TTL=57 Reply from 109.61.91.195: bytes=32 time=10ms TTL=57 Reply from 109.61.91.195: bytes=32 time=10ms TTL=57 Ping statistics for 109.61.91.195: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 10ms, Average = 10ms

Hi, I don't know if you can see it in the screenshot below, but the TDC slew is disabled for the Winwing Orion Throttle. Why is that?

I have a ffbeast but also use the beast hardware trim, since i can change how it feels when i push the trim button. In DCS i loose too much force and it's harder for me to control the stick and the trim.

Hello, I have noticed a (quite minor) issue since the very beginning of the Early Access. The sound of the gun is note synchronized with the gun shots. In fact, the sound is to slow and doesn't have the same rate of fire as the gun : if you shoot a burst, you can hear around 75% of the real shots. If for example you shoot a 20 rounds burst, you can hear only 15 or 16 gun shots. As the M230 as a quite low rate of fire, this discrepancy is really noticable. Especially for short bursts. Did anybody else noticed that and is this issue known by the développers ? Have a nice day.

Took a while to get back.. track files attached. I tried with HOTAS binds and keybinds - same result. I ran a slow repair and deleted the metashader2 and fxo folders beforehand. chinookviews1.trk chinookviews2.trk

I'm guessing that's an issue with the software, or at least the compatibility of the software that you are using to run the iPad as a monitor. The easiest solution would be to buy another actual monitor. That's entirely up to you though. Sorry i can't be of any further help.

What more important thing a pilot during BVR interception would have than watching TID?

If you want to perform true CC where you go straight to the cat after traping you can disable the deck directors in SC special options or just use CVN-74.

My favourite F16 skin work ever. Wonderful weathering effects. Respect @Ala12Rv-watermanpc !

I haven't touched the KW code since leaving PC so I'm a little rusty, but from memory of implementing this it's correct behaviour. I believe the reason you aren't seeing the WP names in the screenshots from the manual is because I turned off the display of the WP names for LINE and AREA graphics when I took those screenshots, specifically because the screen becomes quite cluttered. This can be done in the RMS->SETUP page IIRC. I think this setting affects all pages that display BF graphics, i.e. it's a 'global' setting, not specific to the RMS or HSD pages. Again, I believe that is correct behaviour for the CDS we modelled. As Vakarian mentioned, all BF GRAPHICS are in fact created from WPs and CPs (can't remember if TPs?) and so when importing the drawings from the mission editor, the points of the drawing are constructed as new WPs and added to your WP list. I believe this is discussed in the manual, including the priorities of constructing the WPs from the various possible ME sources.

Heres video of my latest problem - after i returned from summer vacation to DCS, i lunched DCS and puf - problem returned. My main dcs screen escapes to wrong monitor...I have setup like this in pic And heres video link to google drive of my problem https://drive.google.com/file/d/1tzy7a9rMNgW62aN00--geWY-QTzvZJrh/view?usp=drive_link

Hi, Can you say anything about how the PSVR2 compares to the HP G2? How is the wearing comfort, the colours, the resolution, the depth perception, the performance (I use the G2 with 60 Hz)? Thank you!

+20, вес пустой, Это не правильно, в Афгане Ми-8Т, Ми-6, Ми-8ТМ поднимались и летали с грузом на 5000+

I start to think ED will make a Mangusta Helo.....

Stupendo! Complimenti

In Pimax' Crystal Super settings guide for DCS they recommend using the sharpening of NVidia GPU upscaling. https://pimax.com/de/pages/pimax-crystal-super-the-ultimate-dcs-setup-guide?_s=_s-l-f Does the sharpness slider in Pimax Play replace, override or mirror the sharpness slider of the GPU upscaling settings in Nvidia Control Panel?

I’ve been flying it quite a bit. I have been trying to adjust the roll and yaw setting and it still drifts. Admittedly it is a lot more stable than it was and the startup is a bit more realistic. I’m not a pilot but it just seems like a piston engine reaction now.

If you're on the SteamVR Beta (2.13) please opt out for now. There's an issue with it that will be solved shortly.

UP

Thanks gulredel.

I can confirm and this is something that should be addressed. Question is: does it only happen in DCS? I don't have any other VR games which feature similar dark environments. Maybe somebody else can check. Night flying in DCS has always been a problem. In general I think gamma (and colors in general) has always been a problem in DCS. So this might also be a bad combination of DCS' poor gamma solution and the Supers color issues: If I use the general recommendation of seeing contrast to -1 and brightness to -3 in PIMAX Play I get good colors and contrast in daytime in DCS. Same settings at night crush blacks heavily. Back to stock and you get the color halos. I don't know if PIMAX plans to do something about the colors of the Super, it if the above workaround will be their "solution". The local dimming sliders does not help at all with the halos. The only way to get rid of them is to crush blacks entirely. In the meantime: Has anyone found a good setting for profiles.json that MissionCMDR mentioned above?

Hi guys. I am sure there have been posts about this but I couldnt really find anything specific to my system. I am new to this and need some help. I have some flickering on edges. Not on the edges of the field of view but on hard edges on the terrain and other planes. Could you help me with a setting that will work with my system or do I need to upgrade? System: Pimax Crystal light NVIDIA GeForce RTX 4070 Intel Core i7 14700K 20 Cores 32GB RAM null