Czar

Search for TrackNP instead of 'IR' in the end. I own one. It is very good. (I bet it is the same one @Avi is pointing out.) Because of absurd import and consumption taxes, in some place in the world, original Track IR is an absolute wallet wrecker. I'm using it on this video with the active IR emitter. Precision mode turned off in the Track IR app. Edit: to avoid 100% subject being off from the thread topic. If you want always the virtual stick off, there is an option in the DCS menus to keep them off at spawn. Ka-50 has no binding to hide the stick. If FC aircraft virtual sticks are always showing even with the option to show the sticks set to 'OFF' in the menus, it means they are not available to be toggled off anyways.

Can you confirm the same difference with the POV at exact same place? Ghosting is highly sensitive on different angles and zoom. Looks impressive.

I see. Understood. That's more on the marketing side than anything else. It doesn't mean work is not being done daily. Anyways, we're all excited to see new things. Happy flying

You have to take into consideration that the Phantom is a highly mechanical aircraft systems wise where DCS is already well developed in that front. Who knows how many codes from scratch the Eurofighter module needs or even core updates to get there. We don't know that. The public only has a very limited access to the overall progress of any product, and that 'progress' is more of a marketing technique rather than a pure behind the scenes.

-If the name of your SSD given by the system is the name of an old HDD that was using that sata slot, remove the drive through windows device manager with 'right click -> "uninstall device" and then restart the PC. I had swapped a smaller SSD to a new one and had the issue where the hardware was kept until I done the "uninstall device" command and then restarted windows. It should build back an internal ID of the correct hardware name. No need to open the PC physically. -Reduce Preload radius -Make sure your pagefile is on a SSD. (NVME recommended) and it doesn't need to be massive as 60gb. 30gb is already pushing. -Try Visibility Range on Ultra instead of Extreme. -Make sure you don't have too much bloat on your system as in active background apps. -Remove or Reduce overclocks made on CPU outside factory settings.

The radar doesn't and shouldn't operate with weight on wheels (on the ground). Edit: Seems about right. Bellow, source. https://wiki.hoggitworld.com/view/F/A-18C Air-to-Air Radar The F/A-18C Hornet is equipped with the AN/APG-73 pulse-Doppler Radar which provides multiple modes of operation for air-to-air (A/A) target detection, acquisition, and engagement. The Hornet's A/A avionics suite allows for efficient single crew manipulation of the Radar in both beyond visual range (BVR) battle and within visual range (WVR) dogfight environments. The A/A systems integrate onboard Radar and offboard Datalink information to provide the pilot a sensor-fuzed Multi-Source Integration (MSI) picture. The MSI picture as well as the manipulation of the Radar as a sensor is provided on the primary three A/A formats: Radar/Attack Format - The Attack format is a top-down, B-scope view of the attack region, which is the 140° area in front of the aircraft reachable by the Radar gimbal limits. The Attack format allows for manipulation of all Radar functions such as operating modes and scan settings. Furthermore, it is the only format that displays the raw returns of the Radar ("hits") instead of only MSI trackfiles. The Attack format also provides A/A weapon cuing, allowing the pilot to stay "heads down" in a beyond visual range engagement. Azimuth/Elevation (Az/El) Format - The Az/El format provides a forward-looking boresight projection of MSI trackfiles. It covers the attack region in azimuth (±70°) and up to ±70° in elevation. Radar scan centering and acquisition is available from the Az/El format. The Az/El is also the primary interface for cuing the Combined Interrogator/Transponder (CIT) to do IFF interrogations. Furthermore, the FLIR can be pointed via the Az/El format and be slaved to any trackfile. Situation Awareness (SA) Format - The SA format provides a top-down display of MSI trackfiles around the aircraft. In particular, this allows the pilot to see MSI Datalink trackfiles behind the aircraft the view of the Attack and Az/El formats. It doubles as a navigation display with many of the same options as the HSI format. The SA displays expanded trackfile information, though is not a direct interface with any Radar functions. The Radar itself is controlled by a knob on the right console. This is the only Radar control not done through the avionic system. It has 4 positions: OFF: The Radar is powered off. STBY: The Radar is powered on but not scanning. OPR: The Radar is powered on and scanning, and will power off in the event of a failsafe being triggered. PULL EMERG: The Radar is powered on and scanning, and will not power off for any reason except physical failure. When there is weight on wheels (WoW), the Radar will not scan, regardless of knob position.<<<<< Air-to-Ground Radar The Hornet's AN/APG-73 Radar system provides the ability to paint a picture of the ground in various processing modes, make ground designations, and can also initiate a track (a traditional 'lock') on a surface hit. This section will cover the air-to-ground capabilities of the Radar. The A/G Radar is accessed via the Radar/Attack (RDR ATTK) in the NAV and A/G master modes with the SURF (Surface) option. Entering A/G master mode automatically brings up the Attack format in Surface (A/G) mode. A/G is the default mode when invoking the Attack format in NAV or A/G, although the A/A Radar can still be selected. In A/A master mode, the A/G Radar is unavailable. The Radar itself is controlled by a knob on the right console. It has 4 positions: OFF: The Radar is powered off. STBY: The Radar is powered on but not scanning. OPR: The Radar is powered on and scanning, and will power off in the event of a failsafe being triggered. PULL EMERG: The Radar is powered on and scanning, and will not power off for any reason except physical failure. When there is weight on wheels (WoW), the Radar will not scan, regardless of knob position.<<<< Please, don't fry the ground crew.

Hi, Mitor. Do the following: Make an Exclusion on the whole DCS root folder on your anti virus, including windows defender. Do a repair. Usual path for files and folder exclusion management (windows 11 in english): Search for "windows security" in the search bar Virus & Threat Protection At 'Virus & Threat Protection Settings', click on 'manage settings' Bottom of the page click on 'add or remove exclusions' Add the whole DCS root Folder.

Oh right, apologies Max. I saw your post with the logs but somehow missed that last part of the earlier post. Maybe pointing out once again can be enough reinforcement to get attention to that part. Sometimes we're in tunnel vision and miss some steps that are given to us. I'm very guilty of that sometimes. All the modules affected does seems to be a first indeed. Hopefully OP gets everything going. I wonder if we all need to go to Linux one day (including DCS, ofc) for this issue to stop appearing around other folks.

Hi Mike. Do the following: Make an Exclusion on the whole DCS root folder on your anti virus, including windows defender. Do a repair. (yes, once again) Usual path for files and folder exclusion management (windows 11 in english): Search for "windows security" in the search bar Virus & Threat Protection At 'Virus & Threat Protection Settings', click on 'manage settings' Bottom of the page click on 'add or remove exclusions' Add the whole DCS root Folder. Maybe stuff isn't normal and it is not apparent. Anti virus, including Windows Defender usually instant act upon known files taken as 'threats'. I haven't got this issue, so this comes from other experiences. Item 1 is very important, or everything else will fail. I'm skeptical about drive failure or corruption, but if all else fails, do a check disk command to make sure your drive is ok. Search for: "CHKDSK" and "diskdrive get status" on the web.

hi, that's unfortunate. I don't know any other fix as deleting the shaders in 'saved games' resolved for me. There will be a patch today, perhaps it can help resolve the issue. Delete the FXO and Metashaders2 folders once again just to be sure.

Notice how one argument conflicts with the other. Still is confusing. /Edit* (again) Any evidence for this? ....while ED themselves are making the MiG-29 with laser scanning/photogrammetry? Did ED needed to do a talking & managing AI for us to have Jester? Did ED needed to do ground breaking radar techniques first for us to have the M-2000C and the F-15E radars? Also the little helmet visor thing? Did ED needed to do first a 'Full Fidelity' supersonic aircraft with a dedicated FCAS for supersonic flight for us to have the MiG-21? It also had the first cockpit scan if I remember correctly and the first ground clutter in the radar. That 100% not how this all works. At all. That's not how commercial flight simulation was born and it is currently managed.... All the modules are built from compromises and fairy dust in many places. The only valid argument on the whole thing is the ratio of this fairy dust. Sure, the 35 will have a lot...but if the devs have the passion and want to make it, so be it. I still have my F-4E, F-14, 16, 18... In my opinion: in no way this discourages 3rd party down the line either. All 3rd party wants to be better than the other and mainly ED. That's how competition works and it is healthy...DCS W moved forward with that. Competition in quality is not really on the shortage, at all.

So is it laser scanning the issue? Anything to prove this? In one instance you points at 3rd party doing better than ED. In the other you say ED influences 3rd party to not go the extra mile like HB does. Confusing....

Can this be backed up by data and not just feelings? What if the devs want to do a 35 anyways and the only other way is to wait 20+ years? In 20 years this module can have a massive head start too. Seems too much fear for not enough substance. I don't recall any flight sim developer lowering their bars because of a product success, to the contrary actually.

Sorry, but all the fire and explosion effects on the video are already inside the sim (they are nice indeed). Their wow factor is due to proper editing increasing their value. The only effect in the video I'm not familiar with are the impact effects on the building from the APC cannon rounds. Maybe they are already in the sim, but I can't know for sure as I spend way too much time high up with fixed wings.

A supportive argument: It doesn't have air to ground (not widely used) so it can make up for it with these variants.

It has been stated on few pages back on the beginning-ish of the thread. The team that would be working on a FF Su-27/30/35 is busy with the MiG-29. Likely in the future.

I'm more inclined towards cold war stuff, so I have no interest on the 35 (I'm never saying 'never on this, though). I but I have to say that it is really an exciting moment seeing DCS World from its inception to a F-35 being announced. Feels surreal. I wish ED the best of luck on that endeavor. This comes from countless hours of fun throughout the years DCS has provided me since A-10C early access. I just had to post it.

Yes. This is the info I was after. Thanks for clarifying! Many don't do it.

Wait... ...so the shaders does rebuild themselves up or this is unrelated to the ones inside FXO and Metashaders2 folders? You didn't mentioned that you delete these two folders at every patch on your comment. I'm familiar with the difference in load times after a major patch. I was referring to the load times after those two folders are deleted. Which for me is very close to the same results as having them compared to a previous boot on the same version build. We might be talking about different scenarios, so I just want to clarify stuff. No intention to make prolonged arguing. For me, the way things are with the shaders is a non-issue.

I haven't noticed it at all on a NVME and I don't remember it on a sata SSD. Non issue, maybe? I'd chose a compulsory shader rebuild at every DCS update, than having to face stuff like this from time to time.

Enable "G-Forces in cockpit" on DCS options. It can help a little in a few occasions, if you haven't.

yeahh.................To be fair, ED changed a whole lot on shaders when adding the fog and I only think a couple of times of this fix being actually useful before, beyond placebo effects in 12 years. I'm glad this fixed it for you. I agree on shaders being rebuilt on DCS updates. It has no major effect on performance the first time it is built anyways.

@VampireNZ I had this. I fixed it with deleting the FXO and METASHADERS2 folders inside 'Saved games/DCS'. <OS drive>:\Users\<your username in your machine>\Saved Games\DCS The issue never returned.

Well, if anything helps, excluding the saved games folder (Shaders and scripts) from the equation can be a good thing if you perhaps haven't done it so already. Maybe it's something else is delaying the DLL loading and it is in that folder. Rename DCS folder in the 'saved games' folder to something like DCS.OLD so you can keep your stuff instead of deleting it. Copy and paste your inputs folder into the new one DCS will generate after a single boot (or you can manually make a 'DCS' folder before launching the sim) so you can actually fly. Should look like DCS/Config/Input. If you never see the issue again, might be something in that folder indeed.

Looks like many of you would not survive DCS A-10C and Ka-50 early days.