netizensmith

Cheers. Didn't read stuff properly and thought we all had to land at Batumi initially lol.

Yeah same thing again. When I set my Radio for TBLISI and hit spacebar nothing happens. I guess I'm doing it wrong; I have 2 TBLISI entries on the frequency chart? Perhaps I should instruct my wingmen to land first? Is that possible?

Was really enjoying this right up until all 3 of my wingmen went to take a look at Davey Jones' Locker as I was landing at Batumi!

They were gold. Now they are useless sadly. These need updating; such a shame to let them fester.

The original Razbam pocket guide for the harrier does specify that they will not be able to fully implement this system. We will get a subset, which I'm fine with as I knew that going in.

They are a nightmare yes. In my experience after switching from TPOD to IRMV the Mav will never actually be locked on the target but instead of TDC down I just slew it about a bit until it locks. This now works quite well. What I have found is that if I make a mistake in the button presses on the TDC then I can get the system into a state wher nothing works anymore I.e. I can't slew the TPOD or the DMT,sometimes requiring me to quit out and start again. Next time it happens I'll upload a track for Razbam to take a look at.

My landings are so far removed from those ^^^ lmao.

Yep I got the pink back on a SAM testing MP mission I downloaded. TRIXX no longer installed but it's still there. The issue in my case seems to be if I have sharpening on but don't need it e.g. if I run DCS at 2160x1440 (native screen res) with sharpening on then I get pink. If I drop DCS to 1080p then I get yellow. If I go back to 1440p but turn sharpening off then again I get yellow. TL;DR sharpening on when not needed = pink (in my case). EDIT: OK it's just random. Sometimes it's pink and sometimes it isn't

I do. Trixx used to upscale from 1142 vertical to 1440. I changed it to upscale from 1080p to 1440p and that sent my display black and when I hard booted Radeon reckoned I had no Radeon drivers installed! I deleted Trixx and resinstalled radeon driver and now I have no PINK even though I set DCS to render at 1080p and have Sharpening on int Radeon (on a 1440p display). The real test would be for you to disable Trixx and make no other changes and see if the pink goes. Also we have discovered that Trixx does some very low level shit under the hood and can break your machine quite easily so be careful!

You're not running Sapphire Trixx as well are you?

Same here. 5600XT. Not tried with sharpening off but will give it a go later.

In 2d, on the ground, at night I'm showing 140fps. If I TDC right to get FLIR up on the MFD that drops to 90fps. Double TDC depress to get FLIR on the HUD and it drops to 70fps, so I've halved my performance by doing this. Bringing NVG up only has about a 3FPS impact. Is this expected behaviour? Thanks!

@RAZBAM_ELMOHi! Can you please confirm you/developers understand that the new stroke outline functionality has had an adverse effect, for everyone i.e. 2D monitor users, VR users and MFD Export users? The fix provided currently is for exported MFD users only, and incomplete as far as I understand in that no one knows while file to put the fixed LUA script into. At the moment we feel like our concerns have not been fully understood. Many thanks

@Fri13Yeah I know how to comment code mate. This is a dirty quick hack, not a fix and I didn't expect it to go through code review

Good grief that makes so much sense now I think about it!

No problem! I follow with interest. I'm actually able to VTOL on a carrier or Tarawa quite well but not because I know the right way to do it, just I've tried enough times that I kinda manage to do it ok now. Learning others tips and advice is valuable.

Thanks so much. I took a look just now after what you said. My throttle was too low and I think I’d been trimming to keep my velocity vector level rather that using the throttle and not checking my aoa at all! I’ve spent more time learning weapons, takeoffs and landings. Need to spend some more time learning to just fly. Thanks again

Multiplayer mission, me in an AV-8B and a friend in a Hornet. All going well til about half and hour/40 minutes in when, at about 250 knots my plane's nose starts dipping, I start to pull back to stop it whilst giving more throttle at the same time but the dop continues until I'm pulling all the way back, then I role to the left, try to compensate but end up in a downward spiral until I hit the earth. I'm assuming I did something wrong. I'm very far from an expert in the Harrier. I have the track file but it's 98MB so I can't attach it. Is there some common n00b mistake I may have made? Dropbox shared link for anyone who has the time and inclination to try and help! https://www.dropbox.com/s/on064sznqj9gr6k/A Dish Served Cold-20210207-173710.trk?dl=0

Whilst some of the posts do seem to be needlessly aggressive, I could not have been clearer in stating, and showing via screenshots, that this is a global issue, no matter where your mfds are being displayed and yet that was ignored in the initial response and in every response since. There are three reasons I can think of that we got to this point, a) devs/community liaison not reading what I and many others wrote (a poor show), b) not understanding what I and others wrote (English not first language is the only way you couldn’t understand it though), or c) deliberately ignoring it to make the problem go away. I can think of a way to fix a (I suspect Elmo is overworked dealing with the Harrier plus the other Razbam modules) or b but not c. Is there a fourth explanation I haven’t thought of? Edit: I do not have any issue with the developers. Bugs happen. It’s a fact of life. The pain point sits between the developers and the community I’m afraid but I do have sympathy here.

I also cannot get an IRMAV to launch but I was never 100% sure on what I was supposed to do so I'll follow this thread with interest.

At first glance it does look like I've done nothing! I wanted to keep the default values readable so people could judge the settings they might want to use.

Look again. The default values are commented out (with --) and replaced with 0.2 for the outline values. Change these values per your preference. 0.2 works well for me with an HP Reverb and at 1440p 2D screen.

The gain down 50 clicks, contrast down 10 clicks is the simplest workaround at the moment IMO. Alternatively a Mods\Aircraft\AV8BNA\Cockpit\Displays\Display_StrokesDef.lua that looks like this if you can't be arsed doing the clicking each time: stroke_thickness = 0.5 stroke_fuzziness = 0.4 -- Currently is used for DMC generated fonts black outline DMC_outline_thickness = 0.2 --stroke_thickness * 3 DMC_outline_fuzziness = 0.2 --stroke_fuzziness * 1.1 DMC_stroke_thickness = 0.65 DMC_stroke_fuzziness = 0.42

No, we should comment in the bug thread now, particularly as the response isn't satisfactory i.e. they see it as an issue when exporting MFDs only as far as I can tell.

I already raised the bug and they have responded