Jartsev

Well, for some reason 'Jump to the end if...' logic for both routes in your test scenario has 'Before checking, wait: 0:02' set, and this 2-second wait time causes all the mess.

Yes, this seems to be a problem, so it would be a good idea to check temperatures. Another matter, why this happens; judging by graphics card model, we are talking about laptop, and its cooling system may not have sufficient airflow. Also Radeon Pro 560 is not so much a performer, and may be it is worth to consider reduction of resolution, graphics and terrain details distance settings.

1) What was scenario name? 2) Is there any specific direction of viewing or particular event, when frame rate drop happens? Or frame rate falls down no matter of what, without any apparent reason?

Very likely scenario is set on some old map, which wasn't georeferenced; in such case in v.4.1 coordinates for the map's SW corner are automatically set to Oceanic Pole of inaccessibility, which is located in southern part of Pacific Ocean and this conflicts with time zone settings in scenario. You need to open scenario in the mission editor and then adjust local time zone(UTC offset) in 'Mission date and time settings' dialog.

1) Ability to set 'Embark if...' and 'Retreat back if...' conditions is available in mission editor and during the planning phase only, and those options cannot be accessed during execution phase(e.g. after green 'Start' button was clicked). This is how it works for about 15 years or so now. 2) If you need to coordinate movement of dismounts and their vehicle during execution phase, then waypoint, where troops are are going to dismount, should not have tactics set, and route originating from this waypoint should have slow speed enabled. If speed is higher than 'slow', then vehicles will ignore dismounts; and the same thing happens if waypoint has some battle position tactics enabled and user gives command 'Proceed' or 'Resume route' to a vehicle.

Quite opposite. This switch sets minimal lase range threshold, because in particular case of LRF relying on first return logic this is the only way to eliminate false returns caused by ground clutter and different masks(objects). E.g., if this switch set to '1200', then any returns closer than 1200 meters will be ignored; if it is set to '1800' , then everything below 1800 meters will be ignored... and in default '0' position it allows returns within 500-3000meters or, in favorable visibility conditions- 500-4000meters.

BTW- page 34 of 3.0 release notes. My bad.

Acoustic shot detection system, which slews RWS on to source of incoming fire It literally means 50x spotting scope. Please note that 50x scope is not zeroed, and cannot be used as a sight. This option reflects certain changes made to Lemur; for more details please check pg.7 of v.3.0 release notes: https://www.esimgames.com/wp-content/uploads/2016/03/SBProPE_3_Release_Notes.pdf

This issue is fixed in current beta version.

Those are legit questions, and 90$ are still a considerable sum of money, if purchase of computer game is considered.

We prefer not to disclose our plans, since they are subject to change. As a rule of the thumb, we are announcing new features when release of major update or upgrade is close enough. Yes, if vehicle has interior modelled, then some of elements are usually made interactive, depending of data available and some other considerations. Well, our AI is semi-automatic, so it relies on user-defined control logic to operate in realistic way. On its own AI could handle simple things like, for example, taking cover or adjusting position to engage target of opportunity.

Here is link to their website, but please be aware, that currently there is no english language version: https://syberion.tech/ P.S. My strictly personal gut feeling is whispering to wait till first series production devices show up.

Well, it depends... Nominally your computer more or less fits minimal system requirements listed here: https://www.esimgames.com/?post_type=elementor-popup&p=1160 ...But in practical terms all depends of your graphics settings, terrain detail distance rendering settings, scale of scenarios and many other variables. Also , when it comes to gaming, everyone has his own zone of comfort... Probably the best option is to pick 1 month time-limited license and give it a try before making more costly decisions. P.S. Please make sure that you are running 64-bit version of Windows.

Ok, thanks. So it happens in WAN sessions only, got it

With Marder everything is pretty much straightforward, but I cannot reproduce problem with Pizarro in the LAN session with several instances of SB Pro PE v.4.167 running at the same computer... Are there any specific steps?