SnapRoll

Here my setup, built around a VPC Desk Mount. Will probably paint it at some point…

My thread got buried in the mods section... Try this, maybe it works for you as well. https://forums.eagle.ru/showpost.php?p=4422969&postcount=3

This, by the way, works also like a charm for the F-16 HUD. Mods\aircraft\F-16C\Cockpit\Scripts\Displays\HUD\indicator\HUD_init.lua shaderLineParamsUpdatable = false It would also work for the HMD, but I did not like it too much.

Hi BIGNEWY, thanks for your reply. I suppose it is a tough one to answer… In comparison to the previous version the cockpit lightning has changed dramatically. It was probably overdone before, but I would still expect some more lights in the dark corners of the cockpit. Switching the lights on and off during daytime does nothing, except for those few spots. Not sure if the light is to weak or the cockpit too dark, I would just expect to be able to see the gauges better. Comparing the old image and the new one, I must admit though the new one looks much more realistic. At night the cockpit looks gorgeous, but still there is just a very intense blackness to it, even when the lights are turned up to full power. Cheers PS: The old image is 2 years old but the cockpit lights were about the same before the last patch.

Hi! Thanks a lot for your answer, but I saw it too late. Was playing around myself and found the same thing. Could have saved myself an hour if I was checking this thread :-) My solution is the following: Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\MDG_strokesDefs.lua stroke_thickness = 1.0 stroke_fuzziness = 0.7 Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\HUD_AVQ32\indicator\AVQ32_init.lua shaderLineParamsUpdatable = false Mods\aircraft\FA-18C\Cockpit\Scripts\HMD\indicator\HMD_init.lua shaderLineParamsUpdatable = false The values in MDG_strokesDefs.lua will make the HUD as well as the HMD lines thicker again, even with shaderLineParamsUpdatable set to false. Also this makes the display exports more intense. I have not tested what side effects these might have. But for the moment it looks quite good.

As of today's update, the cockpit lights have no effect. Tested during daylight quick mission.

As you may have noticed, they've done some nice changes to the MFD exports. The MFDs exports now have very sharp thin lines and even the night mode is still readable. The HUD, on the other hand, has very ugly thick lines. I am not even sure if they are the same as before, because I used to mod MDG_strokesDefs.lua to make them thinner. My problem is now that when I change: stroke_thickness = 0.8 stroke_fuzziness = 0.5 to lower values, the MFD exports get very dim. The AMPCD export can be corrected with the other variables in this lua, but not the outer two MFDs. Has anyone found a solution to this already? My main display runs at 4k.

That’s the default size. I am running 4k, zoomed in and only cut the HUD out for posting this picture.

I’ve just tested it again and if I take IFLOLS as a reference I get a bolter and if I only use ICSL I get a _OK_ 3-wire. I took a screenshot from the cockpit with ICLS lined up and also at the exact same time from the LSO station. I think it is pretty clear that something is off with IFLOLS. The LSO screenshot also shows that the ship is not pitching at this time, so all this stabilizing stuff can be ignored.

I get that, and normally I am doing this, but keep messing up as I get close. This time I just carried on, kind of like: ICLS is high, IFLOLS is low, I go through the middle. I was surprised that I got the 3 wire and was not short as of IFLOLS. Not that I know, but I find it a bit much of a discrepancy between the two systems. In the documentation it says that ICLS is not gyro-stabilized. This was the Super Carrier Cold Start Mission in Persian Gulf and the ship wasn't pitching that much.

To my surprise I just had a “_OK_ : WIRE# 3” landing… normally, the line reads much longer… but that is not the point. Look at the attached picture, why would ICLS show high, while IFLOLS shows low, and then on top I get a _OK_ landing. Is this a WIP thing or is this to be expected in close? I’am at today’s Beta: 2.5.6.50726

As the title says...

The first picture is showing the Ghost Velocity Vector above the horizon while the Velocity Vector is below. This is happening in landing configuration. The second Picture is showing a 6.4G turn and it looks weird that the Ghost Velocity Vector should be leading.

You probably have "easy communication" enabled which is only using COMM2 (Manual). Once you disable "easy communication" there will be no more grayed out airports/ships but both radios work identical.

Have you read these already? https://forums.eagle.ru/showthread.php?t=179253 https://forums.eagle.ru/showthread.php?t=179314 https://forums.eagle.ru/showthread.php?t=179455 If I were you, I would start with the TF-51D and only once you are able to take off and land effortlessly progress to the Spitfire and then I-16. What kind of hardware are you using as your rudder pedals?

Oh, sorry, I miss read this part. If it does not work with the keyboard directly, than it must be something else.

The problem you are seeing has most likely to do with the duration your virtual button or switch is being pressed. I've seen this in the F/A-18 that some switches need to be pressed for longer then the default of the "pulse" function in TARGET has set. This is the reason you see it in the setup menu react to your button press and also when you press the key by hand, but not when flying. You could use the TARGET function "press" and then "release" with some delay like 50ms or so before the "release" to have the virtual button pressed for longer. Just keep in mind that you need to take care that you always follow a "press" by a "release", otherwise everything can get blocked when your keyboard key is being pressed forever afterwards.

Hi Forexkor I’ve completed the mission now. I’ve just mistaken “the package” for the load to take back. Thanks for your help. SnapRoll

Hi Forexkor Thanks a lot for checking! But how do I leave the load there? Did I miss something during pickup? I’ve landed on the roof @WP2 and let the dialog finish until it said the thing about not exceeding 150Km/h and 5m/s. Does it need some pickup interaction there? If I remember correctly it says automatically that they’ve loaded the chemicals. Regards, SnapRoll Edit: I've just listened to the messages in the mission file and realized after listening to 26.ogg that there must be a sling load nearby. I've must have misunderstood because its says "collected package we can take off" in 28.ogg.

I do not get mission 7 to work. When I land with the cargo at WP3, nothing happens. I am at the latest open beta 2.5.6.45915 Did anyone else encounter the same issue?

Can this get acknowledged?

The first picture you can see how much brighter the in cockpit MFDs are. This problem is visible on every MFD page where there is no black background. So, this would be the moving map, Maverick, targeting pod and Walleye. The second image is the exact same situation, but in external view, and suddenly the brightness seems to be much better. At first, I thought my 8” MFD screens are bad, but then, when you go to full-screen-exclusive (alt-enter), you can see all on your main monitor side by side.

Are you using the TARGET software? Your problem might be that your key command is a "pulse" instead of "hold". You need to depress your button until the speed brake is deployed. A "pulse" would only press your button for a few milliseconds. You would not see the difference in the controller setup page in DCS, as even a pulse would just highlight it. Also be aware that when your gears are out your speed bake auto retracts. when you release the button. I would first test the behavior with your keyboard...

Have you deleted your fxo and matashaders2 folder in your saved games? Have you checked other games?

I have not tested it and yes, I totally agree.