Question Regarding H.sie Patcher

radcapricorn · 01-10-14, 06:02 PM

Yes, normally that's exactly what you should do. Your silenthunter3/data/menu/*.txt files are the ones from the last mod that modifies them. So you should take that and add h.sie's additional strings to it.

But... Think of it like that: every mod you install replaces the files it warns you about. So whatever ends up in your data folders is the most "current" state. Granted, it can be sometimes incorrect i.e. if one mod replaces a file that another one depends on, but in this case it shouldn't really matter. I mean, as long as h.sie's additional strings are there, you should see them. If you don't, then you've either not installed something or the patcher didn't work.

Delta Wolf · 01-10-14, 06:29 PM

Ok..

Seems to work if i dont load the game via SH3 Commander??
Maybe i need to remove all mods roll back and install mods again.

I'll report back...

@radcapricorn Thanks for your help on the ACM Reloaded scope filters....
Worked a treat

radcapricorn · 01-10-14, 06:39 PM

You're welcome

Hmm... If the problem only appears when using SH3Commander... Maybe you have some mod for SH3Commander itself that replaces those files every time you run the game?

Delta Wolf · 01-10-14, 08:51 PM

Hi Guys,

Got it to work by rolling back Commander then removing all mods, then then adding all mods again.......

Guess i must have missed a rollback somewhere between mods

radcapricorn · 01-10-14, 09:37 PM

Use the auto rollback feature, it's invaluable

Glad you've sorted it out. Happy hunting

BigWalleye · 01-11-14, 07:54 AM

Auto Rollback works great - except, what happens if you experience a CTD? CTD does not exit via Commander. Are you now rolled back, or not? Does Commander know how to cope with this situation? If you restart Commander, it recognizes that Auto Rollback is enabled, and does not give you the option to manually roll back. If you then restart SH3 from Commander, it overwrites a new copy of the Commander changes, and saves the "old" files - which already contained the Commander changes. Then, when you exit Commander after this session, it "rolls back" - to the changed files.

So Auto Rollback is a fine idea, as long as you never experience an in-game CTD. A while back, I got myself wrapped around the axle this way. Had to do a complete reinstall. (I know, I know! I should have saved a snapshot! Din't.) Now I use Manual Rollback and always roll back before exiting Commander. If anyone knows a way to avoid this, I'd love to hear about it.

Delta Wolf · 01-11-14, 08:09 AM

Quote:

Originally Posted by BigWalleye

Auto Rollback works great - except, what happens if you experience a CTD? CTD does not exit via Commander. Are you now rolled back, or not? Does Commander know how to cope with this situation? If you restart Commander, it recognizes that Auto Rollback is enabled, and does not give you the option to manually roll back. If you then restart SH3 from Commander, it overwrites a new copy of the Commander changes, and saves the "old" files - which already contained the Commander changes. Then, when you exit Commander after this session, it "rolls back" - to the changed files.

So Auto Rollback is a fine idea, as long as you never experience an in-game CTD. A while back, I got myself wrapped around the axle this way. Had to do a complete reinstall. (I know, I know! I should have saved a snapshot! Din't.) Now I use Manual Rollback and always roll back before exiting Commander. If anyone knows a way to avoid this, I'd love to hear about it.

Thanks for the info Bigwalleye, ill keep that in mind

01-10-14, 06:02 PM	#1
radcapricorn Helmsman Join Date: Jun 2011 Posts: 105 Downloads: 181 Uploads: 0	Yes, normally that's exactly what you should do. Your silenthunter3/data/menu/.txt files are* the ones from the last mod that modifies them. So you should take that and add h.sie's additional strings to it. But... Think of it like that: every mod you install replaces the files it warns you about. So whatever ends up in your data folders is the most "current" state. Granted, it can be sometimes incorrect i.e. if one mod replaces a file that another one depends on, but in this case it shouldn't really matter. I mean, as long as h.sie's additional strings are there, you should see them. If you don't, then you've either not installed something or the patcher didn't work.

01-10-14, 06:29 PM	#2
Delta Wolf Engineer Join Date: Apr 2013 Posts: 209 Downloads: 155 Uploads: 0	Ok.. Seems to work if i dont load the game via SH3 Commander?? Maybe i need to remove all mods roll back and install mods again. I'll report back... @radcapricorn Thanks for your help on the ACM Reloaded scope filters.... Worked a treat

01-10-14, 06:39 PM	#3
radcapricorn Helmsman Join Date: Jun 2011 Posts: 105 Downloads: 181 Uploads: 0	You're welcome Hmm... If the problem only appears when using SH3Commander... Maybe you have some mod for SH3Commander itself that replaces those files every time you run the game?

01-10-14, 08:51 PM	#4
Delta Wolf Engineer Join Date: Apr 2013 Posts: 209 Downloads: 155 Uploads: 0	Hi Guys, Got it to work by rolling back Commander then removing all mods, then then adding all mods again....... Guess i must have missed a rollback somewhere between mods

01-10-14, 09:37 PM	#5
radcapricorn Helmsman Join Date: Jun 2011 Posts: 105 Downloads: 181 Uploads: 0	Use the auto rollback feature, it's invaluable Glad you've sorted it out. Happy hunting

01-11-14, 07:54 AM	#6
BigWalleye Sea Lord Join Date: Jul 2012 Location: On the Eye-lond, mon! Posts: 1,987 Downloads: 465 Uploads: 0	Auto Rollback works great - except, what happens if you experience a CTD? CTD does not exit via Commander. Are you now rolled back, or not? Does Commander know how to cope with this situation? If you restart Commander, it recognizes that Auto Rollback is enabled, and does not give you the option to manually roll back. If you then restart SH3 from Commander, it overwrites a new copy of the Commander changes, and saves the "old" files - which already contained the Commander changes. Then, when you exit Commander after this session, it "rolls back" - to the changed files. So Auto Rollback is a fine idea, as long as you never experience an in-game CTD. A while back, I got myself wrapped around the axle this way. Had to do a complete reinstall. (I know, I know! I should have saved a snapshot! Din't.) Now I use Manual Rollback and always roll back before exiting Commander. If anyone knows a way to avoid this, I'd love to hear about it.