Question on Locking Hud Message Box

[scrapser]

The box where you see the text of crewmembers speaking and announcements of flash traffic has the ability to be locked in place but this must be done again each time you return to a saved mission. Is there a way to set this permanently?

Thanks

[MONOLITH]

The default positions of items can be modded, like the stop watch too; but yes, they always reset to their default start position everytime you restart the game.

I hate that as well.

[scrapser]

I found a mod in the List of Mods thread that addresses this issue but apparently it only works in that mod for 1024x768 screens. I made my own adjustments for 1280x1024 resolution and it works great. Took me about 6 tries to get it where I wanted it.

[jimimadrid]

Please go to this thread and download the JTxE. Unpack in the SH4 Folder
http://www.subsim.com/radioroom/showthread.php?t=123521
You get a new tool like JSGME, but this tool will only merge lines.(In this case in the menu_1024_768.ini)

Put this ini-file in the new Ini_Mods folder.
Ini_File -> http://www.file-upload.net/download-...ition.ini.html

Start the JTxE and activate the MsgboxPosition.

The values are for 1280* 1024 and you will get this:



You can change the red marked values to get your best solution.
Please change only in 10 points to test the new position.
Otherwise you may position it outside the window.



Enjoy it.

[scrapser]

Thanks for pointing out your great modding tool. It will make the tweaking and change management so much easier!

[scrapser]

I made my own INI mod file and loaded it. It's the only INI mod file and now when I try to disable it, I get a message saying I need to remove the file first.

???

The mod file I created is named, "MsgBoxPosition.ini". It tells me I must remove this file before I can disable it. Very confusing.

Should I just delete everything and start over from scratch?

In the ini_Mods folder, I see two files as follows:

"MsgBoxPosition.ini.bak"
"MsgBoxPosition.used"

The second file has a later timestamp than the first. I have no idea what this program is doing. I thought it just swapped lines of code within the file and stored the old line in another file to be swapped back when you disable it.

Would like to solve this and understand it, too.

Thanks

[scrapser]

Forget bothering with this issue. I deleted the whole thing and modified the INI file directly. I kept a copy of the original line of code with a ";" in front of it to comment it out. That way I can restore the original line if I ever need to.

[jimimadrid]

scrapser,

To avoid conflicts with two different mods changing the same lines, the JTxE stores the changed lines in a log. Installing a new ini mod it checks in the log if the line is used.
In some situations i noticed that JtxE get problems when an error during the deinstalling occurs. Than the log lines is not 100 % cleared. Installing the deinstalled mod again gives you the warning that the lines exists.

Manually deleting the loglist.txt in the Sh4 mainfolder solves this problem. I'm working on a version 2.0 where i will solve this prob.

[scrapser]

Originally Posted by jimimadrid

scrapser,

To avoid conflicts with two different mods changing the same lines, the JTxE stores the changed lines in a log. Installing a new ini mod it checks in the log if the line is used.
In some situations i noticed that JtxE get problems when an error during the deinstalling occurs. Than the log lines is not 100 % cleared. Installing the deinstalled mod again gives you the warning that the lines exists.

Manually deleting the loglist.txt in the Sh4 mainfolder solves this problem. I'm working on a version 2.0 where i will solve this prob.

Thanks for following up. I will try this again and see if I can clear the issue. Right now I deleted everything because I started getting an "Error 76" message. I think if I restore the application and try again I may get the same error. Will let you know later tonight when I get home from work.

Another thing I noticed is you must only have lines after a particular key that you are definitely going to use. I had some lines commented out and noticed it would insert those lines (with the ";") into the INI file along with the line I was modding. They didn't do anything but simply added to the confusion.

I will provide examples if you or anyone else is curious.

Can you provide a list of all files that make up this tool? I saw the loglist file and one other but wonder what causes the "Error 76" message.

Thanks again.

[jimimadrid]

Originally Posted by scrapser

Can you provide a list of all files that make up this tool? I saw the loglist file and one other but wonder what causes the "Error 76" message.

There are the loglist.txt and the Modconflict.txt.

JTxE work with ini-files which are located in the ini_Mods folder.

The ini files should contain a target line --> Targetfile=Data\Menu\menu_1024_768.ini
the chapter line --> [IMG]file:///C:/DOKUME%7E1/user/LOKALE%7E1/Temp/moz-screenshot.jpg[/IMG][G3F I248]
the targetline --> Zone=
and in the same line the new text --> 256 764 350 94 0 1 0x3F000000 0.365 0.025 0x3F2A0000 0 0 100 -900

behind this you could put a infotext --> ;1. Message Box position

the infotext should begin with a ; as remarkseparator ( SH4 does not take care of the text behind the separator)

putting remarks lines between the commands will not be writen from JTxE in the targetfile. Therefore i put the remaks behind the new text. This will also help to easy identify the new values in the targetfile.

How JTxE works:
JTxE searches first in the loglist.txt for duplicates of the chapter and targetline.
Getting a hit it informs you that the new mod conflicts with an older mod and ask for install permission, otherwise it install the new mod directly.
After installing, JTxE writes the modded lines in the loglist.txt with the name and date of the mod.
In case of a modconflict JTxE writes the conflict in the modconflict.txt.
The Modconflict.txt is shown in the JTxE window to show the user the conflicting mods. In case of SH4 Problems the user can see where the conflict occurs and can deinstall the conflicting mod.
the ini file in the ini_mods directory is backuped and replaced with the original values of the targetfile. It gets the ending .used. With this file JTxE knows the real values for a proper reinstalling of the Mod.

-- The first time JTxE changes a file it backups this file (menu_1024_768.ini.bak) This will helps to bring manually the original targetfile back.

I hope this helps to understand the logic behind JTxE.

[scrapser]

Looks like I'm back in business. Everything is working. Thanks again for your help...I will be looking forward to version 2.0.