Bukkwild

Repair worked, not the quick one , but the complete one. damaged file or something from the update or something else, either way it is resolved.

Sorry, realize I didnt try without mods installed, didnt occur at first because it works in MT. but here is the log without mods dcs.logand it still doesnt work in ST

I have been in a mission building frenzy and didnt get to try to fly VR since the patch until today, but when I try I have a consistent problem with loading VR in Singe Thread ( I use it sometimes when I am checking missions because its *supposedly* more stable ) and it locks up every time, showing the nose wheel gear of the background jet on the mirror view on my monitor, and nothing but two different beige colors on the headset. I try the Multi-threading client and its fine. Not ready to call this a bug or anything yet but if someone could take a look at the log files and tell me if I am doing something wrong or if anyone knows what difference in MT and ST since the patch would cause it, it would be much appreciated. In the meantime I will continue troubleshooting.dcs_multithread.logdcs_singlethread.log

ty

I am sure I am doing something wrong, but when I try using the hud repeater on one of the MFDs it doesnt show symbology, even though I can see the N-F and Cam modes. Is there something I am not enabling or turning on to have the hud actually repeat?

+1 needed for campaigns desperately. Thanks

There is no option that appears in modelviewer to switch seats, I have seen the option in the Mi-24 to switch seats but that is missing from the 15E. I was able to keep playing with the views until the back came into view, but still not able to quite see what I am looking for. Is there a way to 'anchor' the camera to a specific seat?

I am setting a mission up using the 'Cockpit perform clickable action' and I was looking in the files for the model and unlike other airframes, you cant just click on the second seat in modelviewer2. Is there a second model coming , more to the first model or not at all? I am trying to verify a few switches values in different positions, and they are the values I have expected thus far, so I need to double check.

well said, the intention of this post is not to beat you over it, but to offer a correction of course for future modules to avoid this situation. hopefully you have taken it for what it is. I would hate to see a repeat of this type of history on something else we have been waiting for like the F 15E I have pre-purchased. take all the time to get the weapon loadout right, because it will make for a better, more accurate product we can all be happy with, not more wishful hindsight. If its worth doing right at all, do it right the first time.

how rude, keep your comments to yourself....oh wait....point is try not to be a turd, anyone can obviously make any comment they want

at the end of the day is it better to do the proper amount of research and only release the intended loadout to avoid having to take away our toys. Being committed to improvement is what any good developer should, refine flight performance and such, but something as fundamental as weapon loadouts should be FULLY researched and basically set in stone before any of us consumers has the chance to even touch it, even us 'beta' testers. Because if the argument will remain "we want ultimate realism" then we do too, meaning that these things sorted out before it reaches pilots hands. The idea of this post, in its entirety, is that to avoid negative feelings towards anyone or anything ,its better to have this fundamental stuff figured out. There is no excuse for this, sorry AJ, this s*** should have been done before the harrier was released at all instead of multiple years into development, then we wouldn't have had someone take away something we shouldn't have had.

Well I appreciate the OPTION for realism, or the option for fun. Either way I appreciate WAY more the forethought to avoid this situation altogether. Something I hope they avoid on the 15E.

Are we here to simulate a specific plane or a plane ordered by a specific party ,loaded and FLOWN to their specifications? I think you should stop updates until you get all relevant information and make it correctly the first time instead of constantly having to say sorry we got that completely wrong for what we are trying to simulate, instead here is something completely different that we think will work for the next month. You would have a lot less confusion and a better overall product. Constant dramatic changes to loadouts to conform to the rules someone flew by seems like a silly thing get ppl riled up with. Stop making changes to loadouts piecemeal, do your research, completely. Only then do one last final update to weapon loadouts and then let your product speak for itself, good or bad.

not to beat a dead horse but great job guys!