Jartsev
-
Posts
1,290 -
Joined
-
Last visited
-
Days Won
15
Content Type
Forums
Events
Downloads
Articles
Everything posted by Jartsev
-
It is possible to make changes to those settings during execution phase, but they would take effect not immediately, but once units wold embark new route or arrive to new BP. Also those 'Default behavior in buildings' settings cannot be applied selectively to individual units; they are global for all units owned by session participant (in offline session- party). -
Please contact sales@esimgames.com; it is possible to replace broken CodeMeter stick (for a fee). Also it makes sense to run CmDust diagnostic utility and attach resulting log file to your email to sales, but please DO NOT post this log here, since it contain sensitive data.
-
Well, I just cross-checked 4.023, 4.167 and 4.267 versions of Steel Beasts and do not see any difference, when it comes to handling of vehicle skins. E.g. with assumption that folder and file names are correct, mods were placed to the right folder and respective camo for party was enabled via Mission Editor, current version works exactly same way as it was before.
-
In order to see what is going on, it would be very nice to have original unchanged scenario. Can you upload it, please? Also if map was medited for use with this scenario, it would be good to get it too. Edit: Disregard, I was able to reproduce problem.
-
Remark here: saving a back-up copy of \ProgramData\eSim Games\Steel Beasts\scenarios only makes sense, if several different versions of Steel Beasts are installed on the same computer at the same time. User-created scenarios should be saved to \My Documents\eSim Games\Steel Beasts\My Scenarios, which is never overwritten during SB updates. Same applies in case, if you are editing stock scenario delivered with SB- save it not to 'Scenarios' but to 'My scenarios'.
-
So now it sounds more like CodeMeter Control Center pops up on system start instead of being minimized to tray. If this assumption is correct, solution for the problem could be found in here: Please also note, that CodeMeter Control Center showing up not minimized to system tray on Windows start is not a big deal per se, albeit it could be quite annoying.
-
This is definitely not right, since warning about approaching expiration of time-limited license shall appear only if Steel Beasts is launched, while Classic License(e.g. 'unlimited license') stored on USB key should not trigger such message. So first and most obvious question- are you positively sure, that message displayed is indeed shown by CodeMeter and not, let's say, something else? Then, if message indeed belongs to CodeMeter, is there any chance, that for whatever reason Steel Beasts is set to auto-run on Windows start-up?
-
I mean individual vehicles within recombined unit in the map view and 3D
-
There are still 6 vehicles in resulting unit, just 2 of them are not showing up on the map immediately. Drag unit a bit, for example, and you will see 'em.
-
If you are jumping away from your current position, AI would not keep changes made by you and would apply own settings. This is not a bug and applies to range, ammo, rate of fire etc.
-
T-62, e.g. a vehicle with 115mm smoothbore gun never ever had such thing. T-62A with 100mm rifled gun- is a different story, but it never reached mass production.
-
Thanks, but delta map will not work alone, e.g. without base package. Edit: P.S. Actually yes, it needs base, which we do not have here.
-
...and it would be really nice to have a map for scenario, where crashes were observed...
-
Yes. Story was about T-55, but it is more like urban legend
-
There is no ready racks in T-54/55/62 (albeit US army thinks different), and loading from any rack except wet one in frontal fuel tanks is slowest.
-
Hello. If you have a Classic License, then it would not be affected by re-installation of Windows, since license is stored on USB key and is not bound to your computer's hardware or operating system copy. After re-installing Windows you would need to install SB Pro PE and a CodeMeter runtime (it is is included to SB installer anyway).
-
By default there is no keyboard hotkey assigned to toggle 1st/last return in Leo 2A5(albeit there is assigned Joystick Button #4). So probably you need to assign hotkey yourself- 'Alt. range' entry in 'Controls' menu
-
Well, AI detects targets, because aside of you and AI-controlled gunner, depending of vehicle type and model, there are also AI-controlled loader, AI-controlled driver and AI-controlled dismounts present. Then, if you are multi-crewing, then very likely in most cases there are still some positions left unmanned- usually loader and the driver(and in real life they would report whatever they are able to see). Then finally, since very beginning of SB, even if all available positions are manned by human users, then this still does not fully supress detection routines by AI (this one of the reasons why there is an optional 'Blind' status available).
-
SHIFT alone in context of this particular feature does nothing- note message saying 'Lase to mark position' , which shows up if SHIFT is pressed.
-
1) Feature actually works, when it comes to its original purpose- spot reports for the user's party. This is very easy to see, if player's vehicle is set blind. 2) You need to press both SHIFT and CTRL (or whatever key or button is assigned to fire LRF). Easiest way to do that- bring target in to your binoculars view, so yellow crosshair will be on target. Then press and hold SHIFT( yellow will turn red), and while it still pressed, briefly tap CTRL. 3) This works in F8 and F7 eye and binocular views, but not in CWS, PANO or whatever sight view 4) This does not tell your AI GNR to look or shoot at target detected by you. So it cannot be used reliably for fire control, e.g. if gunner is attracted by something else, he will ignore this new target, until you directly designate target (by slewing turret/gun) or give order to traverse turret. Same applies to unit of several vehicles, but there is not so much options to actually control section/platoon fires in SB, especially in 3D views.
-
Slave gun to PERI to designate target- arrow up hotkey KH HZF mode (KW on Leo 2A4)- Shift+Numpad * ...But it is strongly recommended to go through vehicle-specific tutorials in order to get familiar with controls and functions before playing actual missions.
-
Ok, this one seems to be related to CV9030/9035 mostly.
-
In real life there is no way for the loader to know, if gun, after chambering a fresh round, is actually ready to fire or not. E.g., as a rule of the thumb, he announces 'Up!"( or 'Ready!') when he cleared recoil path, disengaged safety and bustle door( if present) is closed; this has nothing to do with gun being back in coincidence with GPS LOS.
-
There is a folder with broad selection of different documentation installed with Steel Beasts. It includes User Manual and a keyboard charts on several languages. To access this folder open 'Start' menu, then pick 'eSim Games and finally 'Documentation'. Or you can navigate to directory, where SB was installed (by default this is C:\Program Files\eSim Games\SB Pro PE ) and pick Docs folder there.
-
Yes, this might be treated as consistency problem. But at the same time, in order to optimize performance certain things, which are normally not so much visible, are not rendered in some views.
