Nevyn

In my experience you need a steady framerate for trackIR, 60 or 120, it doesn't seem to like anything else. You could also make sure you are in full screen, there are a couple of threads about that here the ED forums, not sure how it would effect you though, a trial and error session would be the best way to figure that one out.

+1

Wow.

Nope, trackir get it's knickers in a knot if the frame rate is not a steady 60 or 120, so a 10 fps, hell even a 5fps loss, makes you want to pull your eyes or go a kick a few puppies, ok maybe not kick puppies but definitely the eyeballs thing.

Yes OP, same amount for frame rate loss, I am building a mission so start in the same place each time (Tblisi), before patch no frame loss, solid 60 capped for track IR, now 5 - 10 fps gone no changes from my side, which turns it into a bit of a stutter fest.

Same problem but only on one module so far, which I bought on steam years ago and then transferred to ED to use with the stand alone version.

"- Ability to merge a mission made on map X with another mission on map Y, including trigger zones, trigger rules, etc" +1.

Also noticed this behavior, seems strange to me, I wish they would just take the 14.325 seconds it will take to fix this and be done, it's so irritating.

I have 1070TI, i7-9600,32GB and running on an NVMe drive, latest nvidia driver and runs pretty good on 2.7, in fact it feels smoother, some parts of syria is a bit of an f-show, but all other maps are . These setting are the same as 2.5 I haven't screwed with it at all. EDIT: I just remembered I adjusted the Clouds setting from STANDARD to ULTRA

Tacview not causing a crash for me.

Getting away from the foul windoze would be great, there are very few things I despise as much as this crappy win10 and I only use it because of DCS, I would drop it in a second if I could and do a dance of joy while doing it. Perhaps I will give wine a go in the near future.

The AI wingman only fires one round per pod when running in on a moving target and then goes around for another attack repeating the same thing. Have not tested a stationary target. Accuracy is also a problem, the one round lands about 30m short of the target (that's a guess as it's difficult to tell the exact distance)

+1 on everything you said.

+1

Lol

I wonder what they talking about.

:thumbup:

Ahhh, thanks mate, good to know.

What the hell is blind flying?

As far as I know the steam version is still 1.2, so thats probably where your problem is. If you using 1.5 then you need to add your key to your DCS files user profile and then it will prompt you to download when you start DCS and log in.

Sure, i5 4690 3.5GHz or MHz or whatever it is 8GB Ram GTX750TI This does not happen all the time, it happens ever now and then, almost like something has got stuck, odd I tell ya.

Pic 1, the new an improved Mig 21 Ion Drive afterburner taken directly out of the USS Enterprise :thumbup: Pic 2 the new and improved EWR system and camo canopy add on :music_whistling: Pic 3 The new and improved ASO-345.43eb :noexpression: These are some of the glitches I am experiencing, just thought I would show you. I think the ASO missing texture has been reported already. The odd thing is it doesn't always happen, some flights are fine others not so much. Also I have been flying my slick for a few weeks, but what I have found is that the MIG21 module for some reason seems to lock up DCS for a little while when exiting the program, the huey does not do it, thats how I noticed that it seems to be your module doing it. Oh and the torch is awesome btw, good job that, much better than before, hope you not going to change it back to the old one.

Ok so it's not just me, I could not be sure of the blades because I have been flying at night and that's when I noticed it, using the NVG, but I also get these things happening too, Belsimtek pimping our rides its seems. :smilewink:

Happy times.

Ahhh ok, so nothing to do with actual aircraft damage, thanks for clearing that up, been driving me nuts for about a week or so, awesome, :thumbup:.