Deano87

Isn't your pitch oscilation related to icing? You mention icing in your post.

Apparenty its reported that Probe Heat wasn't working in the past, I don't know if this has been fixed?

I didn't put the aricraft in a departed state, the pitch oscilations casued by the icing (presumably) along with the loadout I had resulted in a departure from controlled flight. I had my hand off the stick at the time. Also it should be pointed out that pitot heat was on every time I had these issues. Which is why I thought it was weird.

Max fuel flow of 80,000lb per hour. So Yes... Shes thirsty hehe. Its actually more to the point that the F-16 doesn't have much gas. so its usually best to take two bags rather than a centreline. Most QRA jets are setup that way for that reason.

Yeah, good point.

Rotary just below the countermeasures panel.

Not that fast, I had it when I started a descent from a long, high altitude (45k+) , subsonic cruise. Just as I started my descent I noticed the airspeed in the HUD was frozen, ie it wasn’t moving even though I was clearly accelerating. I popped the air brakes and throttled back and was definitely subsonic. But my airspeed in the HUD was still reading the same number. My Mach indication in the HUD shot up from 0.8 to 2.2 in around 10 seconds, at which point the jet started a divergent pitch oscillation, departed and ended up in the traditional F-16 flat spin/ deep stall. My HUD was still reading the same airspeed and mach even though I was in a flat spin. At around 20k feet all the HUD readings rapidly returned to normal and I could use the Pitch Override to get me out of the deep stall/spin. I saved the track but wasn’t much use because I was on an online server and had been for a couple of hours. I’ve tried replicating it in single player and have never been able to. It’s happened to be a few more times. But I’ve never been able to get a track of it.

Hey all. Is there any .lua file I can edit to change that size of these server messages. I fly on Blue Flag and the constant alerts take up a HUGE portion of my vision for a lot of the time. Can anybody help? Please save me from the walls of text!!!

Or just fly AoA and it sorts it all out for you with no math required.

Was that in a low temperature mission? Ive been trying to replicate this and it doesn’t seem to want to do it for me. No idea why , I’ve experienced it unexpectedly several times but never been a le to catch it on a track.

+1

I actually can't get Dual targeting to work in any mode, including PRE with the TGP, as soon as I hit MSL Step I lose lock on the first Maverick. This is since the latest beta patch. EDIT - I figured it out! It works if you use a single Maverick on each pylon. If you use the TER and 2 or 3 Mavericks on the pylon then it wont work, as soon as you hit MSL Step it will drop the first lock, this happens in VIS, BORE and PRE with the TGP. Track attached - Recorded in DCS OB 2.5.6.59625 F-16 Maverick Multi.trk

It can be tricky. Although I haven't seen any issues as bad as this as long as there are no excessive crosswinds involved. I use around 30 curve on the rudder pedals on the Viper in order to smooth things out on the ground, they are basically footrests in flight anyway . I usually put nosewheel steering on as soon as the nose touches down. Make sure both your toe brakes are getting full travel, so you're not doing any asymetric braking. Also are you using Stable or Beta?

I would like it too! But as long as and only if its part of a realistic package. If in a few years they did a 2016 (or newer) era Block 50 as a seperate module or an upgrade or something with all the relevent other updates, New Tape, AIM-120D, AIM-9X Block II, SDPs, JASSM etc.. Hell go crazy and fit a CDU screen like some of the ANG jets have. Then I'd be all for it! I enjoy the APKWS. But I don't see the sense of fitting it to an aircraft which is set 10 years prior to the weapon even being available, and wouldn't have the software upgrades for the aircraft to use it.

That may well be so. But there are A LOT of differences between different Block 50 aircraft of different nations, let alone different blocks of aircraft. Most of the EU models of F-16 are A-MLU jets which are VERY different from a USAF Block 50. And the Hellenic 50s and 52s are very different also. You either model all of those differences and do it properly, or you don't do it at all. And since the F-16 isn't even half done yet I think and discussion of modeling different aircraft is pointless. ED are not interested in making a frankenstein jet which has neat features from a bunch of different aircraft but doesn't actually represent one aircraft properly.

Viper gives me the best performance out of all of EDs modern aircraft modules so It sounds like something else is going on. My Suggestions: I suggest not using instant action free flight missions to compare to other aircraft. These missions often have a lot of other units in to make it feel like a "living world" and sometimes can be very framrate heavy for some reasons (missions weirdness). They are also not all the same for each aircarft so don't allow direct comparisons. So Its best to open up the mission editior, plonk down an aircraft somewhere in a fresh mission, Select the aircraft you want to test, set its skill to "player" and then hit the green button on the left to test the mission. Then you can come back and change the aircraft to another one and test again. Then you know you're making a fair comparison. If in the above comparison the F-16 is still very bad FPS for you then try below. Delete the fxo and metashaders (or/and metashaders2) folders from your C:\Users\*yourname*\Saved Games\DCS.openbeta folder. This will clear out all of DCS's shader caches, expect longer loading times the first time back into the sim as it makes new ones - I do this for every update. Delete or rename the options.lua from the C:\Users\*yourname*\Saved Games\DCS.openbeta\Config folder, you can change it to optionsbackup.lua for instance. This will cause DCS to create a new options lua. Downside of this is that you'll have to go through and set all your options again for your graphics/game and custom options for each aircaft. This can be annoying but I've found it can solve some of my FPS issues, specially after big updates. Note: It won't effect your aircraft keybindings. Its a good idea to take some screenshots or pics on your phone of your option screens so you can easily set them the same afterwards. Set the graphics options as you want and then try the F-16 and see if you have any improvement in FPS.

Hey, now there’s a radical idea!

No they don’t. Each module has a specific production scope which is dictated by the information they have about the aircraft and what they feel they can use. This will dictate the spec and the timeframe of the aircraft modelled. We don’t necessarily get to know the reasons behind those limitations and decisions. It sure doesn’t sound like it, and this isn’t a logical discussion. If ED have given you their statement on the APKWS, Where is the logic in continuing to post about it? No, I’m the exact opposite. The technical facts are that no 2007 USAF/ANG Block 50 F-16C with the tape and other configuration that is being modelled in the sim would ever fire an APKWS. All the currently in service USAF/ANG F-16s wich could use such a weapon are in a different configuration from what’s being modelled. It’s really not that hard to grasp. It’s also the official statement from ED. Your argument boils down to “APKWS would be fun! Why can’t I have it.”

Short Answer : No, it’s still WIP Not as short Answer: The F-16 is designed to be flown at the higher 350-450 knot bracket, and use the higher available G as an advantage. We are quite limited by our pilots current inability to sustain 9G for any meaningful period of time, which takes away one of the Vipers main advantages. The Viper is also very AoA limited compared to the Hornet or Su-27 so if you let it get slow you’ll quickly hit the AoA limit and be stuck there barely pulling 3G while the F-18 or Su-27 can still pull that nose around on you. So the key takeaway from that that is keep it above 350kn. Speed is life for the Viper, use the vertical and don’t play the slow speed game with the Hornet or Su-27. we should get pilot and FM improvements once resources transfer over from the Hornet to the Viper as the Hornet gets closer to completion.

No, they don’t. It doesn’t matter what you “accept”, you have no power in this situation, therefore ED do not NEED to justify their decision to you. They have already answered you, APKWS will not be coming to the Viper. For the reasons already discussed at length. My suggestion to you would be to accept that fact and move on with your life.

Yes, Thats the same thing I've experianced. Only seems to happen in cold missions. If you can replicate it in single player grab a track of it, as I've never managed to do so.

Cold outside air temp? There have been issues with the Airspeed readings in cold conditions, it looks a bit like pitot icing. Which then changes the way the FCS behaves.

Hi Maxtrust, Thanks for your reply. You maybe misunderstood my point. I'm not really looking for advice on how to fly around the issue, I more want to know if its realistic behaviour to the Mig-21 as I've never flown an aircraft (either IRL or virtually) with electric trim that behaves this way. Looking at the issue more closely it seems as though there is a time threshhold which the trim button is required to be pressed in order for the stab trim to move, once that threshhold is passed the trim starts moving, however it will then continue moving for roughly 1/3rd of a second even if the trim switch is no longer being pressed. This is what causes the relativly course trimming feel. It also means that a lot of quick dabs of trim do not get registered at all. And when it does register it will just move to the next 1/3rd of a second step. I have a difficult time believeing this is realistic, and It makes trimming - specailly while flying formation - a real chore. Could we please get a "simplified" trim model where the stabs move as soon as, and for as long as the trim switch is activated. Make it a custom setting if you want. It would make the aircraft much nicer and more natural feeling to fly. IMHO. I've made a short video to show the problem.

Hey all, I'm loving this module, everything feels so analogue and alive. The only issue I'm having at the moment is that the pitch trim seems to feel very notchy and imprecise. I tap nose up trim.... nothing happens, tap it again.... nothing happens... tap it a third time and suddenly it seems to click over to the next notch and I get a load of trim change all of a sudden, It makes the aircraft really difficult to trim out at times. I've actually sat on the ground and watched the stabs from external view, you can actually see them mirroring the above behavior. I can give it taps of trim in either direction and most of the time the stab doesn't move, and then when it does it moves a BIG step to the next trim "notch". Is this some idiosyncrasy of the IRL Mig-21s trimming system or some weirdness in the sim?

I concur. It is not working correctly.