fagulha

I think it´s bugged (not tried myself yet) but you can check in the post below about the IFLOLS Overlay but reading some comments i see that some people are with same issue than you. It´s planned for today a hotfix (let´s hope fixes those issues too). EDIT: the hotfix changelog don´t mentioned this issue https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.16.28157/

I'm at work right now (3 PM here) but when i arrive home (about 10PM) i will test myself to check if it is bugged or something like that. I will reply here when possible ok?

It´s not right. Did you make the calls for landing?

I don´t install anything in the DCS core folder. I use OVGme for mods that need to be installed in DCS core folder. So, i recommend doing the same. With a click you can enable/disable any mods (useful before an update).

You have 2 options in the mod but yes, they reduce the bloom effect. Sorry i couldn´t help you further but something is not right with your IFLOLS lights. Did you make the proper calls for landing? Usually when inbound the deck get ready for aircraft (if at night the rabbit lights will be turned on, if it is CASE I recovery the IFLOLS should be lighted).

I´m using this mod until the IFLOLS bloom will be improved/fixed

It will be excellent if someday will be possible to see in DCS, that if we hit the basket about +2 kts the shockwave, in the hose, when coming back again could ripp off your probe out as it is irl. Using DCS since day one so i believe it will be possible in the future.

I reset my head position (VR user) with default key Num5 and then i use Cockpit Camera Move Right/Left/Up/Down/Fwd/Aft to refine my position to be properly seated. It´s the first thing i do when i start any sortie. And only then i unpause DCS and start my walkaround, climb to aircraft, etc.

Same performance issue below around 800ft. As soon i hit the deck, with F2 view, fps went from 120 to -45. You can try it by yourself. Press F2, adjust the view so you´re on top looking down and zoom out/in and check fps from 800 ft below.

I use the Reaper drone, A-10´s, F-15´s, infantry, etc. A lot of options just check on Mission Editor as stated.

The Portuguese 1991 Tiger Meet liverie for the G91 (Credits in the pic)

Thank you for the tip, and i´m sorry i didn´t see your post earlier so i can try to help you out Keep up! Best regards from Portugal.

Thank you for your reply. Yeah, i already got it working and with IADS script too. Awesome. Best regards, F.

"Sniper XR Targeting Pod."

Hey no worries i was just trying to understand and to be helpful in some sort.

You can disable the IFLOLS pop-up window. I never used it anyway, even when was not possible to disable in DCS options i used a little mod to disable it. I was talking about the physical Meatball blocked by the F-18´s in the boat not about the Meatball Pop-Up window. The meatball will guide you to touchdown, but hey, do whatever works for you because in the end it´s the one thing that matters. Keep up. F.

You shouldn´t be looking to speed or altitude. The only things you need to scan until you land is Meatball, AoA, and Glidscope, nothing more. That´s why i asked why you blocked the IFLOLS.

Thank you!

And a last one of the CV-59 with whiter markings:

I fully agree. That´s why i try to balance that whenever i can at my own needs between reality or usability, i choose the later (i´m using deck liveries with whiter marks so i can spot easier the deck in VR, or, the liverie i posted earlier for improved deck textures, both are a good example).

In a simple search in DCS User Files you´ll find this: https://www.digitalcombatsimulator.com/en/files/3319070/ All carriers in deployment sooner or later get the deck darker due gases, fuel, oil.

+1!

Muito obrigado Eduardo. Going to compare with my missions. Bruno.

Eduardo when you said it works i believed you You´re one user that i always praise your opinion. If don´t be too much trouble to you but can you send me that simple mission so i can compare with mine to check what i´m doing wrong please? Thank you once again, Bruno. EDIT 1: i only get it to work with moose 2.5.0, and albeit my script have c130:Spawn(3) only one is spawned. Going to further testing. EDIT 2: got it to work with latest moose 2.7.10, i just deleted the triggers etc load everything again, changed script for a new one and for the moment it seems it is working. Still can´t find what was the issue... Thank you.