When new version is released? attack direction "relative by enemy position" is not working normally.
It's premium feature. The new editor will be sold as DLC.Why did you remove edit mode? Please restore it. I want to add a lot of objects.
It would be better to get rid of the existing editor when the new editor is completed. I'm curious as to why the existing editor was removed.
how much is it? I'm willing to pay if it restores the default editor that I can use right away and makes it optional.It's premium feature. The new editor will be sold as DLC.
It's a joke. WSE2 is a separate engine, written from scratch. The scene editor is not removed. It is not developed yet.how much is it? I'm willing to pay if it restores the default editor that I can use right away and makes it optional.
When I try to run it, it says that a .dll file is missing.I installed WSE2 latest version, when i try to run the launcher and hit play i get the error: code execution cannot proceed because MSVCR120.DLL was not found.
I installed the microsoft studio and the direct x installer but that hasnt changed anything, currently trying to run it on windows 11. Also when i try to click on options i get an error saying could not open rgl_config.ini.
Any ideas? Thanks
Try running WSE2 with administrator rights or install it on a drive other than CDear author, an error message poped up suddenly upon game's launch, saying:
Error reading application id. Please either write it to steam_appid.txt or use the launcher.
I've no memory that anything has been done to the base game itself by me, also I'm using the warband downloaded directly from this site: https://www.taleworlds.com/en/Games/Warband , yet still a steam_appid.txt file does exist in my game base folder, it says 48700 and I didn't modify it through in any means, so I've no clue what could have possibly gone wrong, what should I do? I'm still at wse2 version 1.1.2.0, is that the cause of it?
Thank you for replying, I did that, checked administrator rights for both wse2_launcher.exe and mb_warband_wse2.exe in properties, and the game base folder installed on Disk F, then run the wse2_launcher.exe. But the same error message still showing, sadly.Try running WSE2 with administrator rights or install it on a drive other than C
Did that, but still no. Also tried do a clean fresh install of the game itself, and updated wse2 to 1.1.2.6, none helped, appreciate for your trying, still. Now I'm starting to think the problem might be on my end, strange but I often run into wierd issues like this, maybe with some times given will have me figure out what's being wrong.Then try delete steam_appid.txt
It's working now that I download the game files from steam directly, definitely got something to do with it. Also I replaced its exe to none-steam version and it still works, I get to open the game normally, play the mod normally. Anyway, I don't know what happened, but anyone encoutering this issue might try this out.Then try delete steam_appid.txt
Ah i insalled the x64 not the x86, it runs now thank you. But i still get an error when i try to go on options in the start up menu, could not open rgl_config.ini.Microsoft Visual C++ 2013 Redistributable Package (x86)
Never mind it fixed itself somehowAh i insalled the x64 not the x86, it runs now thank you. But i still get an error when i try to go on options in the start up menu, could not open rgl_config.ini.
I have the same crash in VC with WSE2. It happens only after saving on the global map, but it's rare and it doesn't replicate after loading. The script in question is also not called by any other script in the module system. If possible, please double-check it somehow, though I have no idea how to force the crash to happen.Party have invalid parent party. This is probably an error in the module scripts
When did you first experience this kind of crash?I have the same crash in VC with WSE2. It happens only after saving on the global map, but it's rare and it doesn't replicate after loading. The script in question is also not called by any other script in the module system. If possible, please double-check it somehow, though I have no idea how to force the crash to happen.
Another thing, the Battle Size slider has too wide of a range, up to 6150 in VC. Makes it a little annoying to use. Can't find a setting that would restrict it.
Re crash: No idea honestly, it feels like it's been happening during my entire current playthrough of VC which I started in July with the most recent version of WSE2 available at that time. Hadn't played for a year before that. I didn't pay it no mind since it's rare and doesn't break the game entirely (plus, the VC devs broke the game in many others ways with their recent patches...). I only realized it might be WSE2-related when I saw another person's comment here.When did you first experience this kind of crash?
The battle size range has been increased specifically so that players don't have to manually increase this value in the config.