Willdass

The Royal Norwegian Air Force have long had a Christmas tradition flying a great star or tree formation across Norway. Sharing the holiday spirit, 23 Norwegian DCS enthusiasts come together to try and fly a similar formation. Ending with a small three ship display.

Not sure why you hit the water or why the tacan does not work. Workes for me. But regarding landing to the side: double check the magnetic heading of the runway in f10 map. The ILS chart says 72° but the magnetic heading for runway 07 is 78° in my missions. Putting 72° will have the ILS command steering cue guiding me to the civilian terminals...

Same for me in FIWOS mission 8. I flew missions 1-7 in 2.9.5 with usually above 70fps in VR (4090, 5800x3D and 64gb). In 2.9.6 I had 45fps at the first half of mission 8 and sub 15fps in the last part. Absolutely unplayable, sometimes below 7fps. No changes in mods, settings.

The TGP follows your current SPI and in CCIP the Pipper is the SPI, so the TGP will just follow the pipper. Hobel is correct. It's also safer to ingress in CCRP as a single missclick on the pickle button won't release your bombs prematurely.

Had the same issue. Try to disable the launcher and for your 2D shortcut add: force_disableVR Worked for me.

Same issue here, will test the solution tomorrrow. Thanks for the find. How is this even possible? It's getting comical at this point, having to change mouse settings in order to have a playable experience, wtf.

Thx! No I haven't updated yet.

I tried it again in the Hornet and got a position pretty to the Display video posted above, but using the same method as with the F-16 I loose the head movements. Strange

Ah OK, I understand. That's too bad

Worked fine for me in the Hornet. Only zoom via "current field of view" slider

@CommandT I did some testing yesterday with the F-16 and was very happy with the result of editing the lua (thanks @buceador) and moving the camera over the shoulder. I used the FOV graphich setting to adjust the zoom and think it worked great. Have you tried that? This also kept the head movements in the track replay. But as soon as I tried to rotate the camera (for example for backwards facing camera on the HUD ) the headtracking was lost. Any tips for that? Or is it best to use external view and move it inside the cockpit for backwards facing GoPro view? This was just a test Short I made and think I came out pretty good: edit: obiously the Short format does not give the best impression of the FOV/zoom but here is a screenshot: null Love your videos btw @CommandT

I have tried. Loosely based on John "Rain" Waters demo videos on Youtube. It might give you some inspiration

I've experienced the same as OP many times. Auto handoff is not reliable, works sometimes but not always. Even with a solid boresight at 7-10nm (D variant), if I try to launch on group of targets, there is a good chance the maverick locks on to a object next to my selected target (auto handoff from TGP). This could be other vehicles or even light posts... Therefore I always feel the need to visually verify the lock on the WPN page , which kind of removes the point of auto handoff from TGP... When it works, it's usually because there are no other heat sources nearby.

Hi @BIGNEWY , possible to get the "Ejection Seat Lever" permanently bindable in the controls? The default.lua file gets rewritten each patch, so it would be great to just have this option in by default Thanks!

Uncage with LG down to declutter the lower part of the HUD & remove ILS info. Useful on short final.

Know a few guys who had similar issues and they got a new units. You might hurry up though because the Aero is now discontinued, so who knows how many spares they have..

@BIGNEWY @NineLine Hi guys, can you please take a look at this? Hopefully a quick fix to revert back to 2.9 NVGs. Thanks!

This patch seems to have reverted back to the old NVGs in VR for me... Last patch it worked fine, but now I have a squared box with the NVG inside following my eye tracking (same as before 2.9). Running Varjo Aero with Varjo Foveated Rendering. Please hotfix this.

Same issue for me. Gross weight 34000lbs, afterburner detent special setting "Always OFF" and can't launch without burner.

I aswell get high fps and stutters in multiplayer, much more noticable on other aircraft when flying formation.. No upscaling, DLAA and sharpening 0.5. Other than that no change in settings compared to 2.8, where I had some stutters but nothing like this. Ping on both me and my FL was about 35

Yes, both windows and GPU driver is up to date. Performed a clean up and repair, same error. Will do.

@Flappie @BIGNEWY Tried a full reinstall of DCS, and Standalone version this time. So I could test with a clean Saved games folder and install path, no mods, no modules installed. Game booted both in VR and 2D. Changed graphics settings to what I had tried with steam version (DLAA on). Game restarted and worked (both in 2d and VR). So I thought I had solved it, thought it was a Steam version bug... But, I closed the game, powered of my HMD to start the game again and install my modules in 2D mode. Now the same error pops up as with Steam version, and I cannot get into the game. See attached for logs. Game crashes both in ST and MT mode. Errors I get: 2023-10-23 10:00:22.682 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{LAU_SNEB68G}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/rockets.lua" 2023-10-23 10:00:22.682 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{LAU_SNEB68_WP}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/rockets.lua" dcs.log-20231023-100139.zip

@Flappie Tested some more. If I apply DLAA and remove it before I close the game, I'm able to start the game back up again (VR and 2D). But if I leave DLAA ON when I close the game, I have to "options.lua.bak" and have to apply all settings again. Tried all your tips under "A" in your linked post, nothing else worked.

dcs.logdcs.log-20231020-114342.zip Tried to change the script lua, did not work. So I tried again with options.lua.bak, game launched. Then I tried to reapply my settings from 2.8 and the game automatically restarted and worked. Then I tried to only apply DLAA and performed a manual game restart, this resulted in a crash. This time though, I did get a crash message and was able to send the report. See attached