Jartsev

Ok, thanks. Those issues are now in the list.

No, this is not about your hardware Use 'toggle magnification' hotkey, please. Reticle is not projected if night optics have 1.8x magnification selected(which is default for Warrior and Scimitar), so in order to see reticle you need to enable high magnification(6.4x). Admittedly this not very obvious.

Yes, unfortunately. Depends of the computer's specs, but still slow.

Interesting. Never experienced such things with GTX1050Ti, which is newer than GTX970, but doubtfully if better.

Ok, thanks, this one is #8068 now. Please note, that not only the CITV is affected.

Thanks, we will look into it...

This was previously reported, but, unfortunately, not yet fixed despite of all programmer's efforts. BTW, try to refresh or replace theme in the scenario- in some cases this may help.

Ok, thanks! Was there a TC damage present?

More moot(or not so moot) questions: -Are you using gunner's or TC's positions? -Since you are experiencing issue while in the test mode of the Mission Editor, was scenario re-saved between test runs?

Supply of effectors is pretty much limited and some of them, covering exact arc were expended previously. You can see this in AAR by tracking previous events happened to this unit; also note- one of previous impacts was quite close to the left side radar and may be damaged it.

Well, this seems to be completely different thing, and may be not so much a bug in fact. You may notice, that with gun over hull side vehicle motion in pitch axis is perceived mostly as sight/gun LOS jolting in roll axis, so it's more about width/shape of the bumps, IMHO. Edit: it is very easy to see from external views how vehicle's hull is moving during off-road driving, and how this affects gun depending of turret azimuth position.

Ok, thaks we will try to investigate this, but from description initially it sounds like a kind of network problem. P.S. Scenario or map where issue was seen would very handy.

Thanks, will investigate.

Yes! Ok, thanks. Themes with 'Realism_' prefix were delivered with SB Pro PE 4.0(or may be earlier) and in fact are obsolete now; current 'stock' themes have '_eSim_' prefix and you will not see such problem with them. Now I'll try to explain what happened... Version 4.1 have additional option for the ground type settings- 'is dirt'. Textures for ground type, which have this option enabled will be also utilized for unfinished or not camouflaged emplacements; if theme doesn't have this option enabled for one (and only one!) ground type, then textures for ground type #0(which is a 'Field' in your case) will be applied to emplacements under construction or without camo. Old themes are still pretty much usable, but you need to enable 'Is dirt' option for the suitable ground type(only one of 16 available in the theme!) first, and after this you will need to update your scenario with fixed theme. Also this thing about flagging ground as dirt should be kept in mind during conversion of pre-4.1 maps.

Actually problem with wrong texture may be indeed theme-related, and this makes me to ask you for scenario where you see it; if scenario is based on custom map, it would be very handy to get it too, or at least a theme file...