DmitriKozlowsky

Silly me. Its just a calibration gradient. Here I was thinking that the MFD can now display grayscale radar and high contrast IR from ATFLIR. Well life is full of disappointments.

Please post screen shot of new A-G radar grayscale option in 2.9.11.4686 My A_G radar on stbd(right) MFD is legacy green-amber. Thank you.

So any clue as to why F-5E leg and remaster so slow in 2.9.11.XXXX? My speculation is that its not using RTX GPU. 3D rendering is all in software or in baseline Windows 3D GPU emulation. I am looking at GPU memory utilization and GPU utilization. in Task Manager GPU memory usage is little below 8 GB. Shared GPU memory usage is 0 GPU 3D utilization is bottomed out. Little better then when running YouTube in Chrome.

OK,I see the dark vehicles on top pic. I see the dark dots on bottom. I never see those on my system. I can see red, I can see blue, but I do not see neutral dark grey or black dots. Not on my rig. Maybe they are there, but its my panel. Its a start. Thank you How do NEUTRAL DOTS look through NVG and in pod FLIR?

JHC! Still nothing. What tells me which course to set? ILS is turned ON. Flight Director? On the manual and on videos those yellow needles are described clearly as ILS needles. CENTER THE NEEDLES, thats what I am being told. What are you talking about? If pilot can screw up ILS just by maladjusting heading, what is the point of ILS guidance. I have no clue what the heck you are talking about. This makes no sense to me. Why would Heading be 291 , not 290 not 289 or 292? I am imagining if I all I see is gray, no visual ques. All I have is my GPS location on map and ILS 'needles'. I fly to intercept ILS beam as shown on map, and I get B.S. feedback on ADI. I need something actionable , not "Becouse you are doing it wrong."

OK. So to get back to the original question. Not really answered, What is a NEUTRAL DOT and what does it look like? What am I suppoused to look for? When labels are set to SYMBOL ONLY, I see red dots for threat and blue for fiendly. But thats too easy and too much of a cheat, especcially at night. So I would expect white or grey dots for neutral. So where are they what do NEUTRAL DOTs look like? I don't see them. They are not drawn, or are drawn in such way that makes them not not apparently visible. Thats why I asked for a someone else's screen grab. What am I looking for? THe simplest questions in DCS have no answers. Or so it seems.

Somebody or something is just gaslighting me. I am not being given accurate instruction. Here is screen cap of ILS approach to Fajurah. ILS 111.50. All set, ILS enabled, ILS needles uncaged. Aircraft is on glideslope for good VFR landing. Gear down, flaps, down, heading set. ILS needles are bullS! Just B.S. If this were CATII or CATIII I would be led to beleive that I am too low, and too the left of runway. I would maneuver and land long or to the left. What makes absolutely ZERO, NONE, ZILCH sense to me, is why adjusting heading screws up the localizer needle. it would jump left to right abruptly, even as I am aligned. The system is lying to me. Noone here is making sense of it. ILS works off radio beams. I intersected those beams. I should not be seeing what I am seeing.

OMG! I ask again. When I am lined up on approach within 10km to Khasab, why are my ILS needles so far off to the side? Why am I being presented with false information on ILS display in ADI?

I mean ILS needles. In fact thats what the YouTube video refers to ILS indicators, as 'needles'. YouTube is ot offcial instruction, but videos are from aviation schools. Good enough for flight sims. So I am still left with no answer, as to why my ILS needles so offcenter on centered stabilized approach to Khasab.

Aviation instruction needs a serious reform. It is inherently difficult to understand and confusing by design. No wonder so many new and aspiring aviators wash out or perish. Theory is well described. Implementation and procedures instruction, kind of suck.

WHAT?? I still don't get why my needles are so off center. So why are my needles so off center?

OK, well then my understanding of ILS, despite hours of YouTube videos, mis sorely off mark. They desctribe two sets of beams. One pair for glideslope, second pair for localiser. ILS field frequency is entered, ILS is enabled. Then beams are intercepted and aircraft flown down to minimums. Nowhere does it say that Course has to be set a particular way in order for beams to give accurate information. So I still don't understand, why, even with course not set, does my A-10CII gives me inaccurate needles.

Just what I am experiencing at 2560X1440@144, no AA. I see nothing, at reasonable distance. By the time I do see anything bigger then a pixel, even a darker pixel, I am being engaged by AAA or 14.5 MG. The most usefull sensor is under AV-8B DMT. That places 'v' symbols on HUD, giving a que where to slew the POD. But then the pod does not show targets, until I get closer, circumventing use of pod. A-10C does not have DMT. DMT works under day and dusk/evening. Not at night. It works via contrast. If AV-8B DMT can see contrasting targets so should virtual camera. Yet I would zoom in vew angle into HUD and all I see are 'v' not the targets themselves. They are invisible. Or appear to be.

I see. ILS has to have course set to give accurate information. But isn't ILS dependant on radio beams? Thats a litte confusing. My WP was set to airfieliefd landing.

I asked for a screenshot of another user's NEUTRAL DOTS with AUTO SIZE. Just as on my system, the other user's screenshot shows me nothing of use to spot ground vehicles. I don't see ground targets. I can't make them out, I do not see spotting neutral dots. To me this is a confirmed issue.

Look, while squinting , look at screen cap. You can just make out the ground vehicles as slightly darker pixels. But this is on frozen scrren cap. In motion, during action, those are tottally lost in noise of NVG, and in daytime, lost in filtering of ground texture. I have AA turned off, as AA makes issue worse. Darkeing intensity of NVG produces more visible noise, and amplifies the problem. Once more, this is a subjective issue for me, but I am also not seeing ground targets in other people's screen shots. Its not that they are hard to see, I don't don't see them at all. The screen grab that was posted. I see nothing! Nothing at all. Trees and roads. Even in a screen cap, I do not see vehicles. Not as 3d objects, not as pixels, not as dots. I started this threat becouse with NEUTRAL DOT and AUTO size, I see no ground targets. They are not visible. Reardless of time of day. In RL, there would be shadows to accentuate targets, but the shadows in DCS are not accentuated enough. Again, I am not seeing ground targets, until I am within few hundred meters. Obviously this is impossible to accomplish anything as far as combat.

Isn;t that 2.2 for SPI target, which is in the distance. He distances are distorted in NVG. The ground point I was aiming at was between 300-350 meters away. Again. Its the size of the target, as it is drawn by DCS. Its far too small, and I cannot see it, day or night.

Negative. In the screencap I am about 300 meters away. About the same is a car as it appears on a large parking mall parking lot . It should be clearly visible, even as a LOD box. There is something not working on my DCS or in DCS period.

This is my typicall issue. Ground targets, like tanks, armored vehicles, day or night (night is worse), are pixel or sub-pixel sized. In effect , they are invisible, untill few hundred meters from target, at which point its too late to do anything. Even at 200-500 meters, ground vehicle is a pixel or two pixel sized box. At night in IR or NVG, foggetboutit! The pixel sized targets are completely lost in noise.

I DO NOT UNDERSTAND. What am I suppoused to see here? Where is anything? Lets say I am ordered to engage? I would 'UNABLE' no eyes on target? This, for me, is DCS wide. Is this one of those color blindness tests, which I am failing. Its DCS wide for me. Ragrdless of units.

Has anyone ever installed DCS on WUBUNTU. https://wubuntu.org/ Its Windows but its Linux but its Windows and I am not sure of either

The visibility may have been caused by Visibility Global set to LOW. I changed it to Med. Hopefully that may solve issue, without FPS drop. I always thought that Visibility global is for terrain.

Rapucha can't hit me from 10km away, when I am at 12,000 with AAA. The mission defbrief stated I was hit by Igla. But in any case, there was no indication of hit. No bang sound, no shaking of aircraft. The only indication was the sudden warning light. Tottally sterile experience. I have a general problem in DCS, of just not seening the threats and targets. I don't see anything! They are so small. Pixel sized, not drawn, or otherwise invisible. Unless I am within 1000 meters of threat. Ships should be clearly vibile from distance, yet they are not. TPOD at max zoom out, scanning is not picking up, untill I am withon 7000-5000 meters. With naval targets, they engage you at 20-30km. I have this mod, FNS Tornio. It engages me at 20-30 km with IR missiles, and I have no warning whatsoever or any situational awareness that I am under threat.

Could someone please post a screenshot of SYMBOLS ONLY and DOT SIZE AUTO spotting dots suppoused to look like. Becouse I see nothing . Acutally, I can't be certain , but I am having serious problems just seeing targets. I don't know at what version this started.Even something as large as Rapucha LST on open ocean, is not visible outsise of 10 km or even closer, with aircraft at 7000 feet. Just not there. TPOD at max zoom out, is not not picking out the hot IR signature in IR mode in A-10C. I would set external view to traget, and I can see own aircraft, but the target is invisible. Ground vehicle are pixel sized or sub-pixel sized untill I am with in 800 meters. I basically don't see anything, even if its shooting at me. I could see tracers rising from ground from ZSU-23 on truck, but the truck itself is invisible. I don't quite get the system here.

I was engaged by IR from Rapucha LST. Likely MANPADS. MWS did nout sound. Countermeasures , set to AUTO, did not release flares. System was ON and audio was at max. There was no smoke trail I had no idea I was even hit. There was no sound in aircraft, there was no shake of cockpit, no nothing. Except the fire warning light on engine. Experience tottally devoid of experience. I don't know how SA is acheoeved when engaged by IR MANPADS, as there is no aids. Whats up with that?