speed-of-heat

I have the following issues 1) On the way out i complete the fence in and the character says i have fenced in but the fence in message in red stays for ages and ages 2) when i RTB there is no debriefing (I get the message saying there is) 3) when i end the mission i just get a hang and have to close the DCS process to recover

I asked the same/similar question a few days ago, in my case it was another weapon that was set to pre forcing the seeker back to the most recent or previous waypoint. Nobody seemed to be sure if this was realistic behaviour or cockup

In some lighting conditions the fuselage is completely black, it looks like its lacking an "alpha channel" or similar ?

great Mission!

or you can add it to your signature file Settings - ED Forums

damn it! i thought i had disabled the A4 mod! it was the A4 mod! however the loadout is still at odd with the briefing and lineup card

same Mission 6 leader does not bomb his targets, also the loadout is different than specified i have 2 120's and 1 9M ?

if its just a dead pilot .. you might be able to edit the logbook lua file and undead him

yes i get the same warning, its not relevant to DCS

when you use the Open XR Layer API , make sure that XRNexcksafer is first

indeed , in the mean time i can play the missions ...

yep this, smooth, can be a little disorientating at first, but you can get used to it very quickly with practice

1) I hope things are going better for you and yours 2) not sure this is already on your bug list, but i don't seem to be able to enter a specific version into the custom version number on updates null

You don't set them to anything... Just use rotation of the head. The only key I have set is centre

as per the title. start up good jets and comms but one never leaves his hanger, this is a new bug as of last update m05 one does not taxi.trk

it works with everything

Thanks @baltic_dragon, i think i have found the issue , and as i am new to the viper i can't tell if this is a "bug" or a "feature" if you use a weapon in PRE and expend it, the targeting pod seems to fix on either the previous target or if you "un designate" it will lock to the previous/current waypoint ... the way of "fixing" the behaviour is after the engagement has finished undesignate and reselect "vis" which seems to "free" up the TGP to look at other things

No, it was a straight question, I'm relatively new to the Viper, and I wanted to know if this was a bug or not, you seem to be implying it's a bug?

I guess the question is, is this behaviour realistic?

so what seemed to be the problem for me was this , i had previously used a MAV in pre mode, and whilst it was still in pre mode, it would not allow me to change the target waypoint, even though i had no mavericks remaining, turning of pre mode on the maverick weapons page enabled me to correctly select the new target

depends on the MB... many will now default to the "loosest" settings , some are even downright smart about it...

how much RAM ? 2/3rds full should be fine assuming you havent got anything else on that disk ? and @Mr_sukebe is correct.

what are your other specs ? on a HDD its a definite yes, already on SSD it will improve but might be its something else slowing you down i'm on a SSD with a 600Mbs transfer rate and i dont see anything like that sort of load time, maybe the first time i go to a map

short answer yes, long answer it depends a lot on your settings, but in VR yes, online in VR definitely also stickjing DCS on an SSD (super cheap) is highly recommended

its unlikely you would see any difference between 3200 and 3000 though a lot would depend on your config... but the edge cases are rare enough to say "don't worry about it"