Deano87

Already reported. There is another report of this literally a few posts down from this one. Try using search before reporting.

Yes. They have to have the same skins as you to see them, send them your skins and they can see them. Simple as that.

I use custom skins online all the time. Not sure what you mean?

Still Present as of 2.5.6.59398 F-16Steerpoint2835.trk F-16Steerpoint3100.trk F-16Steerpoint2992.trk

Hey, I've had a look and I think its all related to this bug. I thought it had been fixed but clearly not. It says reported so I'm not sure its worth filing a new bug report. Edit - I've updated that thread with new tracks showing the issue. But since its already reported it will just be on the list of things to get fixed once the F-16 starts getting some love.

That is the Su-34 model already in the sim... So unless we see a cockpit shot I'd say no.

Hmm That's a new one. apologies for not filing the steerpoint bug report yet. Wanted to wait for the new patch to drop and see if it changed anything. Will get it done tonight.

I fly in VR and I use PointCTRL which makes everything a breeze as its a mouse cursor tied to the end of each index finger. If I want to click and MFD button I just reach up and hit it. And it’s always on my hand so I don’t have to find anything. Honestly can’t imagine flying VR without it.

You have tried renaming your saved games DCS folder and that had no effect?

Have you read this thread and tried the fixes that worked for other ppl?

Yeah... nice idea but its not going to happen. A 2007 USAF/ANG Block 50 is quite a different jet from a modern Block 50. The jets have been upgraded with new software,hardware and weapons over the years and so regardless of how "easy" it would be, it wouldn't at all be realistic, which is what ED are striving for. Perhapse in 10 years time when we can get a 2020 edition of the Viper in the sim with all the fancy current weapons, but until then, nah.

Just compare the build number in the bottom right corner of the DCS main menu to the build number of the change log. That will tell you if you’ve updated or not.

Did you install the update? It’s reasonably large I think. What build are you running? Here is the guide to using it:

Oh sorry. Didn’t see the update.

It’s not out yet is it?

Awesome. Glad you got it working! Those above steps have usually sorted out any of my random issues over the years. I think refreshing the options.lua every now and again isn’t a bad idea as sometimes you don’t even realise you have an issue. Last time I did it I got a nice FPS boost and buildings etc started being visible from a lot further away, even though I had selected the same setting in the graphics menu. No idea what changed but it definitely helped.

Yeah the pitch authority with gear down definitely feels too low imho. My brother (Ex F-16 pilot) commented on it when he tried the sim a while back. Unfortunatly beyond his input and my feeling I don't have any documentation or figures to back it up.

My best guess would be some borked graphics setting which is in the config folder, try deleting the options.lua inside the config folder and see if the crosshair comes back. If that works then you'll just have to manually go through and set your graphics options again inside DCS.

Nah, don't worry, I'll put one together. I'll get it sorted out tomorrow morning.

Try slewing the HUD box onto something, swap soi to MAV and then correct the Mav alignment with where the HUD box is pointing and then hit the boresight OSB? just a thought, haven't tried it.

Hmm, I can't see that would make any difference. Next thing I suggest you try is renaming your whole DCS folder within saved games. Add OLD or BACKUP to the end of the name so DCS will no longer see it (So DSC.openbetaOLD for instance) this will force DCS to create a new one from scratch during the next startup. This will allow you to test and see if there is anything in the old folder that is causing your problem. If it doesn't change anything you can delete the new folder and rename the old one back and it will go back to exactly as it was. Your graphics settings and keybinds are in the old folder so I'd just leave it on default graphics and quickly set some basic F-16 controls to at least allow you to test the mavericks. If with the new folder the Mavericks work as expected then there is something in the old folder causing the problem, but we can cross that bridge when we come to it.

Yes... Yes you can.

I thought this was fixed a while back but clearly not. I will create a thread in the verified bugs section and try and get it reported it with a track etc.

I suggest uninstalling the F-16 and redownloading it. Go to the module manager inside DCS, go to the installed tab and then hit the trash can next to the F-16 row to uninstall it. let it do its thing and then once uninstalled restart DCS and then come back into the module manager, find the F-16 and reinstall. You should keep all your keybinds and mapping etc. I presume you aren’t using any mods for things like MFD readability or brightness that have been released in the past? If so I recommend removing those as they tend to break things with updates. let me know how you get on.

No. You misunderstand. In the past any mission with the pressure setting set anything but default had altitude errors on waypoints. It was nothing to do with your altimeter setting in the aircraft, it was to do with the pressure setting IN the mission. Check it in a mission with default pressure and see if it has the same effect.