Hi everyone
I think I just found a bug in the morale system. When you use cavalry against enemy infantry, the enemy will always fight to the last man with a "eager" status even when it's onesided like sword ashigaru vs katana cavalry. But if you use infantry against infantry, the enemy would waver and rout after suffering heavy casualties.
This only happens after version 1.2.
I have tried to figure myself by changing the morale stat with PFM but even setting morale down to 1 doesnt make an infantry unit rout when fighting cavalry
Originally Posted by vuvihu:
Hi everyone
I think I just found a bug in the morale system. When you use cavalry against enemy infantry, the enemy will always fight to the last man with a "eager" status even when it's onesided like sword ashigaru vs katana cavalry. But if you use infantry against infantry, the enemy would waver and rout after suffering heavy casualties.
This only happens after version 1.2.
I have tried to figure myself by changing the morale stat with PFM but even setting morale down to 1 doesnt make an infantry unit rout when fighting cavalry
Hm, i'll check it out, but are you sure you have not other mods used with S2R+ which could have such an impact? I can't remind such an occurence.
Maybe, this is solved now anyway due to the unit attribute fixes, as for the wrong PFM tabs, which i've fixed now in the hotfix, did you install already the hotfix?
Edit:
Wait, perhaps the scare enemy attribute is bugged, because i observed the same odd thing with No Dachi (got scare enemy like cavalry) vs. Ashigaru Yari in my recent test battles, fighting to the last man. I'll do a quick test.
EDIT
You are right. My test 100% confirmed my assumption for the said code and your discovery. This deserves credit, i'll mention you in the changelog for this observation/discovery.
I'll fix now the bugged "scare enemy" attribute (btw., this must be a vanilla bug with this special attribute) for v1.4.
First two posts are moved ones.
Report here about bugs caused by the S2R+ modding, if you are sure S2R+ content is the reason.
Hi guys,
Just yesterday I began playing a campaign with the Takeda clan and came across two odd things.
1) When you start the campaign you already have some yari ashigaru and a bow ashigaru. I play with ultra unit size and the starting units are smaller compared to the one I recruit which will be 280 men I think.
2) When I play battles, Bow Samurai run out of Ammo after only about 5 volleys. oO is that meant to be the case?
I play with the UnitVariety pack and a music mod.
Hope you can look into this
Originally Posted by Katsuo:
Hi guys,
Just yesterday I began playing a campaign with the Takeda clan and came across two odd things.
1) When you start the campaign you already have some yari ashigaru and a bow ashigaru. I play with ultra unit size and the starting units are smaller compared to the one I recruit which will be 280 men I think.
2) When I play battles, Bow Samurai run out of Ammo after only about 5 volleys. oO is that meant to be the case?
I play with the UnitVariety pack and a music mod.
Hope you can look into this
re 1) No bug whatsoever. Starting units have just the vanilla size.
re 2) No bug as well. Bow Samurai are supposed to be melee units, not skirmishers, they just fire up a few (deadly) arrows and engage in melee.
As for other mods, i highly recommend to use the unit speed reduction mod as well.
Hey,
I'd like to report two things I noticed in my Chosokabe-campaign:
1. Loaned sword ashigaru have a wrong recruitment pic (in recruitment menu's at towns or armies); it's a stretched picture of Bow Ashigaru. Once recruited, they have the right pic though (for instance, when clicking on armies to review units or at the UI in battles).
2. Roads are not constructable after researching the vanilla tech. In the research tree, roads are mentioned both at the original tech (the one just one tier above Chi) and the higher tier one (where you also get a higher level roads). Not sure if this is intended or not.
Using your latest version (1.87), new campaign, year 1548
Additional mods: Movement Speed Reduction Mod, Realm Divide Mod, Extended Campaign Victory and Kinjo's Cherry Blossom Mod (recommended!)
Cheers,
Belgae
Originally Posted by Belgae:
Hey,
I'd like to report two things I noticed in my Chosokabe-campaign:
1. Loaned sword ashigaru have a wrong recruitment pic (in recruitment menu's at towns or armies); it's a stretched picture of Bow Ashigaru. Once recruited, they have the right pic though (for instance, when clicking on armies to review units or at the UI in battles).
2. Roads are not constructable after researching the vanilla tech. In the research tree, roads are mentioned both at the original tech (the one just one tier above Chi) and the higher tier one (where you also get a higher level roads). Not sure if this is intended or not.
Using your latest version (1.87), new campaign, year 1548
Additional mods: Movement Speed Reduction Mod, Realm Divide Mod, Extended Campaign Victory and Kinjo's Cherry Blossom Mod (recommended!)
Cheers,
Belgae
Alright, thanks for the report.
Re 1: While i'm using a unit card mod - i'm having Sword Ashi available from the start when i start a Shimazu campaign, i wasn't able to observe the issue. Although the Shimazu have a faction specific Sword Ashi, the unit cards are the same, so i cannot confirm a bug there. But i'll check it out once more.
Re 2: Road construction requirements (and impacts) have changed, so what you have observed here is correct in the mod.
tan zhi han 07:55 05-14-2011
The game crashes immediately with the latest 1.91 version...
Originally Posted by tan zhi han:
The game crashes immediately with the latest 1.91 version...
I would like to confirm this :/
Same here. Game crashes to desktop after some 10 second on the launch screen.
Have just replaced the upload with 1.90.
Hope that plays with the (suspect) patch from yesterday by CA ;)
Adding this as it fits somehow to the theme:
As i yesterday patched the game i had to remove the roaming S2 folder* to get a working custom battle mode back, formerly the game freezed as i dropped on custom battle mode button - that has been without any mod files in the S2 data folder!
*where the save games, user script, preferences, ui cache, fx cache files live ... some say it's the battle_preferences/.sp_battle_setup.battle_preferences file which makes the anger for the custom battle mode post-patches, so maybe try just to delete this only.
Also i did a game verification via Steam before i patched the game.
Hint: Removing the roaming S2 folder makes no harm to the installation at all, the game generates a new folder when you start the game. It only might be annoying to re-adjust the preferences.script settings (which contain for example all graphics options settings).
I think i found another bug in 1.94
having kisho ninja units in custom battles would make the loading screen freeze at the end of the loading bar, so it might be something texture-ralated.
Originally Posted by vuvihu:
I think i found another bug in 1.94
having kisho ninja units in custom battles would make the loading screen freeze at the end of the loading bar, so it might be something texture-ralated.
Hm, i didn't anything with them. Is this a repeating bug? With every faction as well?
Atm. can't imagine that this is a S2R+ culprit, but i will look myself after it soon (testing them in custom battle).
Edit: I just only balanced their abilities into the mod.
So i did 2 custom battle tests with Kisho's (random faction, Date, me) vs. Sword Ashigaru (Ikko Ikki, AI), one time using them in range mode (blinding grenades), and one time in melee mode: No issues experienced.
yes its a repeating bug, occurs with every faction in the custom battle section. maybe it's just my computer or some mini mods causing the issue then
Originally Posted by vuvihu:
yes its a repeating bug, occurs with every faction in the custom battle section. maybe it's just my computer or some mini mods causing the issue then
My bet goes on the latter case, because why should your pc have issues with one single unit?
Having a CTD when entering custom battle with Sohei-Naginata|Uesugi units using both 1.98 and 1.99. Previous custom battles with stock units worked fine.
Seems to be a texture error but this isn't my area of expertise. Using a gtx260 with driver 8.17.12.7533 the log states:
Downgrading, Over budget by 232 MB
Downgraded Shadows to 3
Downgraded Shadows to 2
Downgraded Sky Options to 2
Downgraded Water Details to 2
Disabled Distortion
Downgraded Texture Quality to 2
I've tried the following remedies with no change in outcome:
-erased the roaming directory and had the program rebuild it automatically
-rolled back divers
-adjusted 3d settings from program choice to performance override
-adjusted game graphics setting from high to medium
-unclicked search for drop in battle
-1.98-->1.99
This seems to be the mod for me and I'd love to get it working. Any thoughts?
I,m not at home right now so I can't check if I get the same results. Hopefully DV can help you soon.
Originally Posted by Nickel? No. Dime? YO!:
Having a CTD when entering custom battle with Sohei-Naginata|Uesugi units using both 1.98 and 1.99. Previous custom battles with stock units worked fine.
Seems to be a texture error but this isn't my area of expertise. Using a gtx260 with driver 8.17.12.7533 the log states:
Downgrading, Over budget by 232 MB
Downgraded Shadows to 3
Downgraded Shadows to 2
Downgraded Sky Options to 2
Downgraded Water Details to 2
Disabled Distortion
Downgraded Texture Quality to 2
I've tried the following remedies with no change in outcome:
-erased the roaming directory and had the program rebuild it automatically
-rolled back divers
-adjusted 3d settings from program choice to performance override
-adjusted game graphics setting from high to medium
-unclicked search for drop in battle
-1.98-->1.99
This seems to be the mod for me and I'd love to get it working. Any thoughts?
Will look into it, if i can replicate the issue, but i wonder how this can be, as the unit is a vanilla unit, to make sure, you mean the
foot Nagi Monk Uesegi, right?
Otherwise it will be thing on your side, do you run other certain mods which have an impact on units?
I don't have any mods running, not even those included in your .zip file. I think it is the footman that is causing the problem. The battle in question is an ambush during the computer's turn. I went back to my autosave and disbanded the monk footman units and the same ambush battle did not CTD when it was the computer's turn again.
Originally Posted by Nickel? No. Dime? YO!:
I don't have any mods running, not even those included in your .zip file. I think it is the footman that is causing the problem. The battle in question is an ambush during the computer's turn. I went back to my autosave and disbanded the monk footman units and the same ambush battle did not CTD when it was the computer's turn again.
I confirm the bug.
Have investigated it in detail, it is in fact the Nagi Monk Uesugi unit causing a crash (in my case a freeze), and nothing else is the reason.
I compared the according files with the ones of vanilla to no avail, also some code test changes for the unit didn't work, atm. at a loss in this regard.
I'll attach the S2R+.pack hotfix to the release post as temporarily solution (crash unit is disabled, replaced with the non-faction-specific one).
Playing Uesugi campaign with the latest version I got a CTD (well the loading screen freezes) when entering the battle. In the stack I had a naginata monk that was given to me as a reward for a finished mission. Maybe that faction specific monk was given to me and thus caused the problem. ??
A very intense campaign again - top notch experience!
Reporting from 1.99.2 version (Uesegi campaign):
Hmm, I still have no info shown when hoovering over the higher castle tiers.
Looks like accomplished mission gives you faction specific naginata monk unit which then causes the crash (freeze) in battle loading screen.
Originally Posted by Hister:
Playing Uesugi campaign with the latest version I got a CTD (well the loading screen freezes) when entering the battle. In the stack I had a naginata monk that was given to me as a reward for a finished mission. Maybe that faction specific monk was given to me and thus caused the problem. ??
A very intense campaign again - top notch experience!
Bold: That is the case (the Uesugi Nagi Monk is bugged somehow). Disbanding this unit is the only way atm..
Originally Posted by Hister:
Reporting from 1.99.2 version (Uesegi campaign):
Hmm, I still have no info shown when hoovering over the higher castle tiers.
Looks like accomplished mission gives you faction specific naginata monk unit which then causes the crash (freeze) in battle loading screen.
Re 1: Strange. Just check that out, when you play another faction, if it is a faction-specific item. Anyway, will look into it.
Re 2: Known. This reward unit must be disbanded.
OK.
Yeah I was having CTDs with the Uesugi also
fireship4 22:12 07-12-2011
I also have this bug, I applied the hotfix after a crash on turn 17 as Takeda when I was attacked by a Uesugi army containing 3 x "Sohei Naginata | Uesugi". The crash still persists when I try to fight the battle, I will try to go back to an earlier save, failing that I will start a new campaign.
Originally Posted by fireship4:
I also have this bug, I applied the hotfix after a crash on turn 17 as Takeda when I was attacked by a Uesugi army containing 3 x "Sohei Naginata | Uesugi". The crash still persists when I try to fight the battle, I will try to go back to an earlier save, failing that I will start a new campaign.
The Hotfix can only work, if a new campaign is started, otherwise Uesugi has recruited already the bugged faction-specific Nagi Monk.
With the hotfix, the bugged unit is disabled completely, except for the case if one plays Uesugi and gets this unit as mission-reward (see above # 24), i hope the AI gets not this unit as reward.
Single Sign On provided by
vBSSO