Jump to content
Steelbeasts.com

Jartsev

Moderators
  • Content Count

    937
  • Joined

  • Last visited

Everything posted by Jartsev

  1. Ok, identified root cause for this issue was fixed.
  2. ...And part about inability to reset selections made in 'Priority of fire' is fixed!
  3. Ugh, this was reported, but not yet fixed
  4. Jartsev

    Kyoat [RESOLVED]

    Hmmm... Judging by your screenshots: 1) 'Query map' inactive button- likely SB Pro Maps Download Manager (SB Pro Map Tools v19) is not installed. Please check this, and, if my assumption is correct you can can get installer here: SB Pro Map Tools v.19 2) Grayed out buttons in the map editor. It looks like that you are trying to edit map with 'Published' status, e.g. read-only. You need to create a copy of such map: open 'File' menu in the Map Editor, then select 'Save map package" and finally choose how to save- "Save as new base package" or 'Save as new delt
  5. With 'Control handle' option enabled? M60A3 is tricky vehicle, when it comes to controls, and in fact here we are dealing 3 separate issues: 1st issue. Palm switches not needed to be depressed to aim the gun. On real vehicle released palm switches are inhibiting traverse and elevation only in POWER mode, but in STAB mode gunner can traverse the turret and elevate gun without depressing them. So in this aspect current behavior is correct. 2nd issue. Palm switches are required to be depressed to fire the main gun/coax. Here I'm not so sure because I don't see an
  6. This is how it supposed to work; creation of conditioned routes(this includes copy-pasting of existing conditioned routes) is allowed only in the mission editor or during planning phase.
  7. Ok... I was able to reproduce the problem, but there is one important catch. This happens only if user attempts to copy-paste route or a route chain during execution phase, e.g. a phase where creation of conditioned routes is not possible- this is why copied conditioned routes doesn't work in such case.
  8. Try to run Windows update: Windows Start menu>Settings>Update&Security> Windows Update> Check for Update
  9. No, you can't apply KB2999226 patch manually by running installer downloaded from MS website. This not how it works with Win 10- you should use Windows Update feature integral to OS(Start>Settings>Update&Security> Windows Update> Check for Update). And as I wrote previously- very likely re-installation of VC++ is needed. I just successfully installed v.4.023 on computer which has just VC++2013 and 2017 installed (both x64 and x86 versions).
  10. 1) Please check, if your computer has Microsoft Visual C++ Redistributable for Visual Studio 2015 installed. -If no, then get installer here: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads -if yes, then uninstall it and re-install using fresh installer obtained via link above 2) Use Windows Update to download and install KB2999226 P.S. Installation(or re-installation) of VC++ 2013 may be required too
  11. I suggest to use export function. Start SB and click 'Controls' entry in the Main Menu. Controls setup dialog will open; in this dialog click 'Export' - in window which will open you will be able to type-in desired name for your backup file. When you click 'Save', exported controls profile will be saved to My Documents\eSim Games\Steel Beasts\export as [your_filename].hkf. You can import it, if needed, from this folder by clicking 'Import' in controls dialog. P.S. Working controls profile itself is stored in C:\Users\<Username>\AppData\Roaming\eSim Games\Steel B
  12. You need to start game in safe mode in order to restore functionality: Start menu>'eSim games'>Troubleshooting>'Steel Beasts Pro PE (safe mode)'. This would reset options to default and start game with 1024x768 resolution in windowed mode. After this you may try to change resolution again. But anyway freezing is something what shouldn't happen, and we would like to see debug log and info about your system. Debug logs can be found in My Documents\eSim Games\Steel Beasts\logs folder; please send logs collected during failed sessions to this mail: ssn
  13. ...Also, it is important to keep in mind, that angle of attack(and hence angle of impact) is different for in-game Spike and Javelin. And this 10-15 degrees difference really matters, because it defines which damage will be inflicted.
  14. Ok, thanks. Those issues are now in the list.
  15. 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.
  16. Yes, unfortunately. Depends of the computer's specs, but still slow.
  17. Interesting. Never experienced such things with GTX1050Ti, which is newer than GTX970, but doubtfully if better.
  18. Ok, thanks, this one is #8068 now. Please note, that not only the CITV is affected.
  19. Thanks, we will look into it...
  20. 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.
  21. Ok, thanks! Was there a TC damage present?
  22. 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?
  23. 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.
×
×
  • Create New...