Floyd1212

Looks like you are missing something. If you look at the first image he posted in the thread, you will see he has "Right Eye" selected for the IHADSS rendering.

I'm not sure your photo is really proving your point. Though the displays are not on, I'm seeing a lot of dust and smudges on the screens, clear reflections of the knees and some wicked blue artifact of the canopy in the TEDAC. I would imagine that if the sun were directly behind you, it would bounce off those screens into your face like a concentrating solar array. As a work-around, I think if you export your displays to a second monitor, those exported displays to not show any glare, and the glare effect is not rendered in the cockpit anymore either.

Also, if you look at the balaclava and where the nose bridge is, shouldn't the image rendered in the left eye show the nose bridge to the right of center? I've never flown in VR, so maybe I just don't understand how the technology works.

On the other hand, think of how difficult it must be for the enemy to see you coming in with the sun directly behind you like that. Surely those Iglas won't be able to tra.....

@BIGNEWY Were you ever able to get someone internal to reproduce this? I get longer texture loading delays after 2.8 (as do other members of my squad) when loading into a mission with multiple slots available. Pick a slot and spawn in, and watch textures inside and outside the aircraft load over 10-15 sec. Prior to 2.8 I had never seen the "floating above the water" condition which is all too often now. i7-9700K | 64GB | NVME SSD | 3090

It is for CPGs that use a 4-way or 8-way hat for slewing the TADS, instead of an analog stick. This setting will let the TADS slew slowly at first, then ramp up the speed the longer you hold it, which allows quick taps on the hat to make small movements.

Some more testing from earlier. This time I performed a lase and store, then slaved to the stored point. (Sorry for me fumbling around trying to figure out what happened as the slaved point was way off to the right of the target and I didn't realize where I was looking.) Then I fired a Lima at the stored point on the ground, and it missed even further to the right. Then I stored another point off to the left, and fired at that, then I tried hitting 3 vehicles and the missiles all went somewhere else. I'm happy to make more videos if they are helpful, but otherwise I will stick to laser-guided missiles to avoid the frustrations. Looking forward to seeing them work properly in a future patch...

When I have seen the "invisible tail" bug happen, the enemy stops engaging you, and you are no longer visible on the F10 map. I think the fact that you can still fly and make it back to the FARP is a bug, and really the aircraft should be considered destroyed at that point.

When you quit back to the Mission Debriefing screen, click "Save Track" and post the file here. Hard to say exactly what is going on without more information about the situation/setup.

Another video, also with poor results. Fired 8 missiles and shacked 4(?) targets at under 5km. I checked INU alignment several times during the engagement and it showed .011, .012, .012, and .003.

Another video showing what is happening in a busy MP environment. I hop to the front seat and fire on a group of units that are relatively out in the open, from a hover. I have also been noticing two explosions happening in slightly different locations, and sometimes with the timing off, where one explosion will happen and then you see the missile enter the screen from above and a second explosion happens.

I'm actually surprised ED didn't release a hot fix for this.

I haven’t watched the track yet, but when you are telling George to switch to RF missiles, are you doing it the WPN page on your MFD, or are you using the “left-long” command to tell George to do it?

Yeah, I feel like they aren't working as intended yet, which is fine, since this is EA after all. I realize the 114L won't be the best solution for all applications, but I am seeing mixed results in settings where there should not be any issues (in my non-expert opinion). I haven't really seen anyone from ED say they are working completely as intended or if they acknowledge there needs to be some tuning in certain scenarios. If anyone at ED want's to test it out on a MP server, let us know. I'm sure you would have plenty of pilots willing to shuttle you to the front lines to demonstrate the problems.

Yeah, I've considered that, but the CMS hat on my stick is quite mushy, but mostly in the "press" direction. It would probably work better than the TMS hat for holding in the "up" direction, though.

I used to get away with not trimming as I came into a hover from speed, and then tapping trim and setting ATT Hold once stable. With the latest patch the aircraft feels more wobbly at low speeds when FTR is not pressed, and trying to settle into a hover. Especially pedal inputs trying to maintain a heading as I also maintain a position. I get more over-corrections back and forth on the pedals than before. Sounds like the latest patch helps stability of the aircraft while FTR is held, which I know is the proper way to do it. Time to remap the FTR button on my Warthog stick so it's easier to press and hold for longer periods. The TMS hat (below the red button) has a very strong return spring, and holding this up for TFR gets fatiguing very quickly.

With software like Helios. Helios lets you place buttons and graphics on a touchscreen, then you export the displays into the middle of those graphics.

Had this happen today with a human CPG with me as PLT. George doesn't seem to cause it to happen, just a human. Should be easy enough for ED to reproduce in a multi-crew setting.

IAT no longer sync's properly in multi-crew. When the feature was released it did not sync properly (as noted in the changelog), then a patch after that fixed it, and now with 2.8.5.40170 it is broken again.

This desync issue is back. Or maybe was never fixed, and has been more apparent for me in the past few days since the last patch that introduced the LST. As part of the startup procedure in a cold start you have to swap seats to turn off LST in the front. At some point George is turning on the laser up front as part of his startup and that turns on NOE/A mode for the aircraft. This didn't occur when George was able to do his complete startup uninterrupted. And I will point out again that the enable/disable for the laser is at L6 on the WPN > UTIL page, and the enable/disable for NOE/A is at L6 on the A/C > UTIL page...

Having Fog of War enabled will only mean they don't show up on the F10 map until they are "spotted" by AI or friendly players. Their threat symbols will still show up on the TSD at mission start based on the "Hidden on MFD" setting regardless of FoW setting.

In addition to the inconsistent behavior of the 114L Hellfires (as noted in other threads), I am seeing a few desync issues in multi-crew that had improved or been fixed, have once again crept back in. For example, when IAT was first introduced the LOS reticle and what the PLT saw in the TADS video feed were different from what the CPG was doing. This was then fixed in a later patch, and is now back again. I am also getting the "NOE" issue where when George (or a human CPG) turns on the laser from the front seat, it will turn on NOE for the PLT in the back seat. This never used to happen with George in the front, but may be cropping up with him now too since you have to swap to the front seat and back again to turn off LST. The IAT desync is particularly frustrating as it appears to me in the back like my CPG is looking somewhere else and engaging the wrong targets.

When you drop a unit in the ME you can check/uncheck the option to "Hide on MFD" for the group. If it is unchecked, the group will show up in the pre-planned "threats" category in the TSD. It's been a while since I have played with it, so I can't recall if only some unit types show up, but I know it works for SAM units. You can search for "threats" and find the pertinent threads. In the future, when/if ED implements the Data Cartridge feature you might be able to plan out a mission and then preload points into the TSD at mission start. Edit: Found these threads: https://forum.dcs.world/topic/319135-placing-targets-in-the-editor/ https://forum.dcs.world/topic/301194-option-for-automatically-importing-mission-editor-targetthreat-control-measure-points/ That second thread is older, and I think some of the issues have been improved upon, but still not perfect

I just tested this myself, and can confirm the BRT adjustment effects the in-cockpit MPDs, but not the display exports. In addition, switching between DAY, NT, and MONO does not impact the external displays.

Oh, maybe I misunderstood. I thought he was using a base with dry clutches tuned such that the stick does stay where you leave it when you remove your hand.