All Activity

DCS (and IL2) already supports native FFB via the old Microsoft protocol, although not all mod developers have bothered to use it. If you have an old stick like a Sidewinder2 it works very well on the warbirds and helicopters and some jets. These old sticks just take the FFB data from the game and that's what you feel. There's no fancy driver software to let you tweek and fiddle, and if the game doesn't provide good or any FFB data (I'm looking at you MSFS) then your experience is going to be disappointing. The Moza stick tries to overcome this limitation by not only reading native FFB data, but also reading general telemetry so that it can create its own effects at appropriate points in the flight envelope. It can make the stick vibrate when the guns are fired, or make it kick if the plane hits turbulence (or the ground) etc. Most of these effects are just a bit of candyfloss really, but they can add something when added to the native FFB. Unfortunately the Moza software just isn't very good at any of this. It's telemetry generated effects are generally just crude buzzing or robotic wobbles and its rendering of native effects is just far too weak. I don't understand why they made such a lovely stick with beefy, powerful motors and then made so many of the effects so weak and feeble. And of course the effects disappear completely when the software crashes or disconnects in the middle of a flight. I think the best thing Moza could do would be to open source the protocol for driving the stick and allow Github to do its stuff, but I don't think that's going to happen. Most of the discussion on the Moza Discord and most of the development effort seems to revolve around just auto matching profiles to aircraft rather than improving the reliability or effects quality. I would suggest that anyone considering buying an AB9 has a good read through the Discord channel first.

Put on psy war op, make it loud.

UPDATE v1.1.3 Quick patch for earlier update fixing (but not completely, can't find a reason at this moment) direction of canopy rain drops. Also added better quality elements and textures inside the cockpit.

We know that the JTAC system needs a thorough re-work, but a small band-aid solution would be a mission editor selection to determine if a JTAC provides coordinates in MGRS or lat/long. If JTACs could read lat/long coordinates, the Tomcat would become a very decent CAS aircraft almost immediately, with the ability to have Jester input the coordinates and cue the TGP to that point. Right now, CAS in the tomcat requires use of the F-10 map, conversion of MGRS to lat/long, and THEN inputting the coordinates in via Jester/RIO. Flying in VR makes that very challenging. I'm assuming that there are other aircraft that can also accept lat/long coordinates and not MGRS, and this simple tweak would open CAS up to these aircraft as well. Obviously dynamic laser-codes and better ordinance selection would also help, but I imagine these fixes are more challenging to implement and would take longer. For the meantime, options for coordinates would provide a pretty significant leap in capability.

I usually fly on AO Aerobatics server, and they have a variety of cargos prespawned into the mission. I can confirm that the barrels do not load. The only ones that load are the small heavy ammo crates, the palletized bombs, and the UH-1 Cargo in a net. It would be nice if the Hind could load up a bunch of the barrels. Maybe even one of the smaller oil tanks (if they dimensionally fit through the opening). It's been really fun to fly with a variety of cargos and feel how the Mi8 responds at different flying weights. With three ammo crates, it even becomes necessary to do a rolling take off, which is extra cool lol!

It's aestethic but I'm not asking the devs, I'm asking if someone here is able to or knows someone who can do it. (I already placed a request on the Skinners Discord, no one replied). That's why I posted here and not under Bugs / problems. "We" means that me and other friends need it cause we are going to fly several cold war missions with the 21 in the upcoming months.

hello. sorry to hear you still have troubles. reinstalling will not correct this issue. one never has to reinstall. i repair will do the same and take much less time. you may try to disable IPv6 on your computer. another thing to check is see if you changed HOSTS file. it is located C:\Windows\System32\drivers\etc. open it with notepad. then post contents here. also in command prompt run ipconfig/all again and post that content.

Maybe.... commercially it's a given hit, but the ball is really in Magnitude 3's corner now. I have a feeling that they are a bit sick and tired with the MiG-21 and wants to work on something new. Also, a true "2.0 edition" would probably mean to start over from scratch. The code is 10+ years old by this point. Perhaps wishful thinking, but a partnership with another 3rd party for a "2.0 edition" might get the ball rolling.

Ну да. Снимающая камера почти упирается в конструкцию ИЛС. Но никто ведь не не летает так, да и камера не глаз. Я имел ввиду с точки зрения восприятия для человека. Тут иногда заходит реальный лётчик 29-го, может он чего-то скажет?

I'm not sure if this would make the developers better understand what the light orb/bloom problem is, but attached is a perfect example of how unrealistic it shows up in game. While this screenshot is of the VR mirror from my flat screen, the blooms actually looks a bit bigger in VR since the pixels are physically closer to your eye. But by showing what it shows up in flat screen, it should demonstrate that this is not a problem that only exists in VR (as some have mentioned in other threads on this topic). I included a zoomed in version that show these lights are coming from the island lighting on the carrier. I'm not sure how bright these are in real life, but even if they are extremely bright marker lights, luminosity should be rendered via brightness of the pixels. Right now I'm starting to wonder if maybe devs chose to express luminosity in clear atmosphere via the size of blooms. This isn't what happens in real life. Somebody perceiving a distant small bright light (in clear weather) would see a bright point source, not a huge bloom. The only way you would perceive a bloom is if you had certain eye conditions, like if you have cataracts or extreme amounts of astigmatism. Or if the light was so extremely bright that it lit up the inside of your eyeball and you start to see the light reflecting off of the inside walls of your eyes. That only happens looking at the sun or if somebody shines a flashlight directly into your eye at close range.

Ask your ISP to provide a public IP, use some valid reasons taht your IP camera, local dvr, or alarm system is not working anymore. If you use some of these reason normally they assign a public ip, dynamic but it will be fine. CGNAT is always a bad thing for gaming in general

Would be great if we could. A while back I had ideas about this, after looking into it a bit I backed off with my tail between my legs. I flew drones around old airfield buildings, control towers, mess buildings, AA towers. I circled everything taking a ton of shots thinking I could transfer it all using photogrammetry and build 3D models. I’d need to take out a mortgage for 3DSMax and fell at the first hurdle. Don’t think Blender would do? I was gonna ask the experts but ah well. Turns out we couldn’t use em anyhow.

Thank you all for what you've shared. I manged to get a totally clean image at last. SSAO got rid of the box shape shown in my initial post but instead I got the flickering veil. Turning of Quadviews companion eliminated the symptom completely... The Problem is FPS without QVC has dropped from 90 down to 63 and stuttering is back bad out the sides of the cockpit. Man frustrating! I want the perf from QVC but cant get around the veil/box. What now, wait for fix? FIXED QVC companion on, QVC foveate sharpness set to 0, PP sharpness set to 0.5 and DCS sharpening set to 0.5

Fixed decal updated https://www.digitalcombatsimulator.com/en/files/3346848/ WIP "AJ" w/ dynamic bort 2017ver

Magnificent, thank you Ugra!

Понятно. Скажите а подвесные баки обозначаются как крылевые на топливомере? Насколько я помню там лампочки баков 1, 2, крыльевой и по-моему лампочка 1/2. И можно ли как-то поставить чтобы сначала с подвесных брал топливо? П.С. Ничего не понимаю. Поставил на стоянке два подвесных бака, оба справа, с полным топливом. При включении электросети загорелась циферка один. Но через какое-то время она погасла. Почему так?

I am a long term G1/G2 user. I recently bought a Quest 3 along with a Kiwi H4 headstrap and Kiwi link charging cable. In spite of several weeks of fairly extensive tweaking I never got the Q3 to perform as well at the G2 and found the image quality, whilst excellent close up to be inferior when looking out of the cockpit. Also I had repeated occurrences of the dreaded water/debris in charging cable error which filled the screen and required fumbling for a controller to remove - typically at the most inopportune times whilst flying or racing! As an alternative I tried Virtual Desktop using a dedicated access point that runs at around 830Mbps which I though seems decent but some research show proper gaming routers are well in excess of. As the return window got closer I ended up returning it, the Oasis driver was released and the G2 is running nicely with Windows 11 24H2, so all good. However, reading reviews where people describe the Q3 as an upgrade I can't help feeling I missed a trick somewhere. Virtual Desktop was very poor compared to the link cable, so presumably a router/access point upgrade is necessary. What recommendation are there? Compared to the G2 the Q3 link cable wasn't as smooth. That said I find SteamVR motion reprojection smoother than the Microsoft one so always ran OpenXR with SteamVR as the runtime (maybe unusual?) Visually as mentioned I found the Q3's pancake lenses brilliant at displaying gauges and edge to edge clarity but the distance stuff seemed more blurry than the G2. A prime example is taking off, the runway looks detailed close up but halfway down suddenly turns into a blurry mess. Maybe it is because the image is so clear the LOD changes look more apparent. Again am I missing some settings in DCS, nVidia control panel or something else to make this less apparent? It is also especially noticeable in sim arcing where the track is great in front of the car but terrible in the distance. Is any of this fixable or am I limited by the compressed image over USB compared to DisplayPort? I appreciate VR can be quite subjective and maybe the G2 suits me more than the Q3 but was interested to hear from those who have had both specifically relating to DCS.

I haven't compared with Intel but the 9800x3d is a monster. I played with overclocking when I first got it and got some very good results then realised I did not need to when paired with an rtx5080. I might need to when I get a 6090 though

@DLEGION You are aware there is an AutoStart facility. 90% of pilots insist on a cold starts. You have the option.

You didn't look at the Official Events feed. There is a mission going on right now for the European group, and there will be one for the American and Canadian contingent this afternoon at 1700 PDT. We had one on the 10th and another on the 5th. There are numerous missions throughout the week, posted in that thread, that you can sign up for and participate in. There are no restrictions for U.S. and Canadian players to fly the European missions, and vice versa. The server is continuously running, but password-protected. I would direct you to my other DCS gang I fly with if you flew more than warbirds, but we do fly them as well. WWII, Korean-inspired (Corsair, Sabre, MiG-15), Cold War, and Modern Jets. That's the Addicted to DCS group, "AtD". They fly Tues, Thurs, and Saturday at 1900 PDT. Their server is not up all the time, and it is password-protected when it is. And they are a carrier-based group, flying F/A-18, F-14, F-4, A-4E, F4U's from carriers, and we have some who like to fly the Harrier, and F-16. There are also some twisted individuals who fly Egg-beaters.... The AtD boss is an ex-Army helo pilot, and retired Erickson's Skycrane pilot. You would learn a lot in either group. Sorry you passed up the 58th.... However, I can send you a Discord invite to AtD if you'd like, via PM....... aka AG-51... When the F6F comes out, we will be flying it as VF-51 off the USS San Jacinto as soon as they make Escort Carriers.. LOL. They have their F-4 and F-14s in VF-51 colors, too.

What he simply meant was how you use the 3 beacon points The normal before spawn method only allowed you to assign 6 points, but not the 3 beacons. With DTC, you can assign beacon points. What he meant was that they don’t have to be beacons, you could make them any spot you want and it will work. But I don’t think he really went into why you shouldn’t do that. Your whole dead reckoning nav system is pretty inaccurate and only with RSBN correction is it “good.” So if you want to have correction when at the front, you will want to assign those 3 points to beacons proper. That’s all it was.

@BIGNEWY @NineLineAny chances this could be a easy addition to the mission editor?

I think we will get It. I just don't know the timeline for this.

We have the same issue on CPG spawn with ending in CTD, either hot start, cold start, dynamic spawn will make a different. This Issue starts first with the last Update. dcs.20250911-192549.log dcs.20250911-192956.log I didn´t use OneDrive on my Gaming PC, so unfortunately may not the problem core. WARNING BACKENDCOMMON (23708): Need to reprocess [DDS] image '/textures/ah64_pilot_seat_all_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format 2025-09-11 19:25:53.056 ERROR EDCORE (Main): Failed to move I:\Gespeicherte Spiele\DCS\Tracks\Multiplayer\vJaBoG32_STTR_Template-20250911-200335.trk.writing to I:\Gespeicherte Spiele\DCS\Tracks\Multiplayer\vJaBoG32_STTR_Template-20250911-200335.trk: Zugriff verweigert 2025-09-11 19:25:53.057 INFO APP (Main): Removed I:\Gespeicherte Spiele\DCS\Logs\dcs.20250911-192549.crash 2025-09-11 19:25:53.153 INFO APP (Main): Removed I:\Gespeicherte Spiele\DCS\Logs\dcs.20250911-192549.dmp 2025-09-11 19:26:24.045 INFO APP (Main): Removed I:\Gespeicherte Spiele\DCS\Logs\dxdiag.txt 2025-09-11 19:26:24.045 ERROR EDCORE (Main): Can't open file 'I:\Gespeicherte Spiele\DCS\Logs\voice_chat.log' from real path fs. 2025-09-11 19:26:24.045 INFO APP (Main): failed to open 'I:\Gespeicherte Spiele\DCS\Logs\voice_chat.log' for reading