What is this mysterious warning?

[Tango589]

I'm trying to run SH3+GWX3.0+h.sie V16B1. Everything went swimmingly up until today, but now my laptop hangs at the 'Not so long ago...' screen. When I open the task manager I can see the SilentHunter tab is available, but so is a mysterious 'Warning' tab from SH3. I can't see what this warning says as my laptop stops wanting to play ball. Can anyone shed some light on it?

[Tango589]

I've now managed to see what the warning says: Menu ID not found:0xf800001!

Then I close it and another warning appears: Meu ID not found: 0x26ac00ff!

Then another: Menu ID not found: 0x26ac0001!

These keep appearing with different ID's until I close SH3 via Task Manager. Has anything vital broken?

Cheers

[Tango589]

Update 2: I plugged the flash drive with SH3 into my wifes' laptop and AVG said there was a virus under F:Ubisoft/Silenthunter hich was cleaned off. This may have something to do with it...

The plot thickens!

[diesel97]

Your A/V software has picked up the mdofied sh3 .exe as a false positive virus signature - try making a virus-scan exception in your A/V software if you have that option.

All the best.

[Tango589]

Cheers for the advice diesel97. My work laptop that I use at home for subsimming has never had a problem with the modified files, but that could be because it's using McAfee(!).

My sh3.exe file has now vanished, so I've pasted in a copy of the .exe patched to GWX3 from the installation I've got runnning for WSM 3. I'll have to re-patch it to v1.6B1 and see how it goes from there.
Wish me luck!

[sublynx]

Menu ID not found: 0x26ac0001?

I get these kind of messages when there is a problem in menu_1024_768.ini file. GWX changes that file, but as far as I can remember H.sie's mod does not.

However I do think that the problem might be the virus detection software and you should first try diesel97's solution.

If that does not solve the problem, you might want to check your mod list. Many mods change menu_1024_768.ini file and that file is tricky modwise. Check for any mods that change the menu file.

[badwolf]

That's great news.
Now Jimbuna would say now "Sink them all".

[badwolf]

Here's an example of what I mean:-

Entry in menu_1024_768.ini

[G26 I88]
Name=AOB dial
Type=1031;Stat bmp array
ItemID=0x260E0002
ParentID=0x260E0000
Pos=17,-14,154,144
Materials=1
Display=2;Linear
Mat 0=data/menu/gui/Periscope.tga
Crop 0=0.606445,0.750977,0.150391,0.140625
MatFlags=0x21
TexFmt=0x9
Drag=false
BmpState=1
NeedFocus=true
SelOne=false
IdGroup=0
StatesColors=0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF

Now it will look for the 0x260E0002

Here it is in Dials.cfg

[Dial37]
Name=PerAngleOnBow
Type=42; DIAL_TGT_ANG_ON_BOW
Cmd=Set_tgt_sel_value
Dial=0x260E0002
CrtVal=0x260E0001
NewVal=0x0
DialVal=-180,180
RealVal=-180,180; degrees
Circular=Yes
CmdOnDrag=Yes

If this entry in Dials.cfg is missing or has a different ItemID due to another mod, you get the message - Menu ID not found:0x260E0002!

[badwolf]

I haven't used the V16B1-Patch-Kit yet, but having a quick read in the pdf, it changes a few files as well as the exe. These changes need to be kept in and not removed by later mods so you'll need to merge them in later mods.

I see 3 conflicting mods (Greyed out) that you need to check.

The OLC GUI 1.2.7 (which was one of the greyed ones) changes a lot of the main files and so can cause problems with most mods not compatible with it. That mod makes huge changes to the menu_1024_768.ini, Dials.cfg and Cameras.dat Thats why I usually install OLC GUI first, then merge later mods in to run ok.

Majority of your mods are eye candy and should install with no problem.

As BigWalleye said, check the !BACKUP folder (may be invisible, so may need a window setting change) to see what mod is overwriting which file.



In my Mods folder, I have a folder called "Merged". I then install my mods one by one and any file that conflicts, I copy it to the Merge folder with the correct jsgme folder path, by merging these files I get a stable installation. This leaves the original mods unchanged and so uncorrupted.
I then install the "Merged" folder last and it overwrites all the conflicting files with the merged new ones. You don't have to worry about order of the mods, long as the "Merged" is last.
Or you might decide to take out the conflicting files in the mods and just have the Merged ones. This will then make the greyed out conflict work correctly in jsgme, that should show no conflicts then. Any later mods you install will then be easy to spot if they conflict, because you'll see a Mod or the Merged folder greyed out. Save any files removed in a suitably named structured folder, so you know where to put them back.