OK, the LAST AND FINAL CALL for SH3Cmdr additions!

JScones · 05-06-06, 06:45 AM

I am close to finalising SH3Cmdr Release 2.6 - the final SH3Cmdr. So far the changes include:

- Added ability to change crew officer faces (includes 3D head and hat wearing)
- Crew transfer message now includes crewman's main qualification
- Added ability to randomise main screen banner (banners by Beery, jcwolf, JonZ and Tikigod have been included)
- Added new "Static settings" feature
- 'FileType' parameter no longer required in "Randomised events.cfg" file
- Added ability to generate randomised events by year ("Randomised events_1939.cfg" and so on)
- Improved backup mechanism for files scene.dat and Basic.cfg

I've also spent a fair bit of time cleaning up all the Cfg files to remove redundant data issues.

Basically, I think I now have SH3Cmdr at a place where it can continue to evolve without the need for me to release updates. I have just a few more planned additions and it will be ready.

SOOO...here is your LAST EVER chance to make suggestions for inclusions/corrections/whatever. Of course, I'll decide what's included based on complexity and time to implement, but if you don't ask...

HEMISENT · 05-06-06, 07:21 AM

Malfunction files ready to go. 1939-1945/7 seperate year Randomized events_19XX.CFG files completed/tested. Zipping up now.

What about the Sabotage folders which are year/month specific?

Salvadoreno · 05-06-06, 07:25 AM

add an overhaul feature. Where after about 3-6 patrols your boat is radomly selected for an overhaul and a few months go by ingame when u sail again.

JScones · 05-06-06, 07:27 AM

Quote:

Originally Posted by HEMISENT

Malfunction files ready to go. 1939-1945/7 seperate year Randomized events_19XX.CFG files completed/tested. Zipping up now.

What about the Sabotage folders which are year/month specific?

Cool. Just send me the randomised events files first. With regard to the sabotage folders, can you just email me a list of the dates and events settings, kinda like as if they *were* added to Randomised events.cfg? I mean, I really don't need to physically see the folder structure, just the settings and dates so I can best determine how to build the option.

HEMISENT · 05-06-06, 07:51 AM

Jaesen
Just E mailed the 7 Randomized Events_19XX.CFG files .
I'll will work on the Sabotage numbers with their respective dates and percentages over the weekend and PM them to you hopefully by tomorrow night. If I get a chance I may be able to wrap up the malfunctions for Type II's also - I really would like to finish this whole thing and move on.

I'm dying to play around with Gouldjg's Chaos files.

JScones · 05-06-06, 08:04 AM

@Hemisent. Wow, you have been busy! What it says to me is that the way I had planned to build the malfunctions feature won't work because it would be too linear.

So, can you pls just confirm for me exactly what you want to be able to change month by month within each year? Is it just the "ChooseFrom" probability aspect (ie 20% chance between Jan and May then 50% between Jun and Dec)? Or the settings as well (Crash depth set to 100m between Jan and May and 150 between Jun and Dec)? I suspect the former, which if so *should* just require a minor adjustment to the current Randomised events file. But pls let me know if it's the latter too. I have two potential solutions in mind at the moment, one revolving around "ChooseFrom" and one being the addition of a new optional paramater "ApplyToMonths".

BTW, how did you find using the Randomised events feature? Any comments or feedback?

HEMISENT · 05-06-06, 08:40 AM

Quote:

Originally Posted by JScones

So, can you pls just confirm for me exactly what you want to be able to change month by month within each year? Is it just the "ChooseFrom" probability aspect (ie 20% chance between Jan and May then 50% between Jun and Dec)? Or the settings as well (Crash depth set to 100m between Jan and May and 150 between Jun and Dec)? I suspect the former, which if so *should* just require a minor adjustment to the current Randomised events file. I'll ponder anyway...

BTW, how did you find using the feature?

The "ChooseFrom" is all that changes. The settings pretty much stay the same but the percentages dictated by the "ChooseFrom" line are what changes. eg 1939 setting x=15%, 1940 setting x=18% etc-(Does that make sense?)

Question
using your lateral thinking theme from a few days ago-
Can I do this?
seperate actions using the same file.
*For testing purposes only*

[0_data\Library\Cameras.dat]
;Randomly adjusts blur duration time to simulate periscope seal/lens integrity,
FileType=B
ChooseFrom=8 ;50% chance-if Commander does not pick one will it move to the below files?
RndMidPat=1

0_x2ECD=20 ;Attack Periscope Drops duration[4]
0_x2EE2=20 ;Attack Periscope Blur duration[3]
1_x2ECD=37
1_x2EE2=37
2_x2ECD=60
2_x2EE2=60
3_x2ECD=3600
3_x2EE2=3600
;--------------------------------------------------------------------
[1_data\Library\Cameras.dat]
;Randomly disables attack scope zoom, simulates periscope magnification breakdown.

FileType=B
ChooseFrom=4 ;50% chance-if Commander does not pick one will it move to the below file?
RndMidPat=1

0_x302F=1.5
0_x304E=1.5
1_x302F=6.0
1_x304E=6.0
;--------------------------------------------------------------------
[2_data\Library\Cameras.dat]*this is a combination of the above two files*
;Randomly adjusts blur duration time and disables attack scope zoom to
simulate periscope seal/lens integrity combined with inoperative magnification

FileType=B
ChooseFrom=2
RndMidPat=1

0_x2ECD=20
0_x2EE2=20
0_x302F=1.5 ;Zoom
0_x304E=1.5 ;Zoom
1_x2ECD=20
1_x2EE2=20
1_x302F=6.0
1_x304E=6.0
;--------------------------------------------------------------------

Sabotage files have potential for numerous events all using the same file-mostly it's the NSS_U boatx.sim file. In the Random folder structure it works fine but using Randomized events.CFG I had problems with conflicting files shutting each other out. If the avove example will work then that solves my problem. If it will not work then I have to completely rewrite the Sabotage files in a format that is Randomized events.CFG friendly

The new feature is great-still trying to fully understand Static settings tho but want to get these randoms completed before I get involved in "static"

Beery · 05-06-06, 08:48 AM

Hehe, I know you already know this Jaesen, but what the heck - one last chance to plug the Patrol Log feature. Please please pretty please - Patrol Log, Patrol Log, Patrol Log!

After all, what's not to like - we'll get a real patrol log out of it for every mission, updated with the events as they happened. It's a way to relive our battles - to remember our greatest missions. Just imagine - you complete a patrol, fire up SH3 Commander, and you get to read an authentic log of events. You can see when you fired your first torpedo; you can see when the merchant finally sank. You'll see how many depth charge attacks you underwent, and how many times you saw enemy aircraft. It will even remind you of the weather conditions - all of this without having to scroll through the repetetive and useless info of the game's patrol log data files. Even after a year you'll be able to go back and look at your favourite commander's logs and say "Oh yeah, I remember that patrol. That was the best patrol" and you'll see exactly what made the patrol so amazing. Things you had forgotten will come flooding back as you read through the log's timeline. You'll gaze in wonder as you find that you survived 50 depth charge attacks. Man, that would be awesome. You already know the greatness of the Commander history feature - probably one of the top three features of SH3 Commander. I'm certain that a working patrol log will also be among the top five, since, like the Commander history feature, it creates a story from our games. This is a feature we've already spent time developing. You've already thought out the mechanics of it, and I've filled out (as best I could) the patrol.log text file based on your instructions. Please say you'll complete it.

We know it can be done, we know it would make SH3 Commander even better. Don't let fatigue get the better of us. Think of it like this - we've been under severe depth charge attacks. We're stuck on the bottom, we've been working for 24 hours straight to save the boat. One last effort at the pumps will get the ship rising to the surface before we're out of air. Let's make that final effort and take our boat home!

I realise that it's mostly my fault that this feature hasn't already been done. You put the ball in my court on this issue and I dropped it, and when I picked it up again the game was nearly over. If I hadn't lost the will to mod during the last few months, this thing would probably be done already. I wish I could go back and change things, but I can't. All I can say is that I know I'll regret it if this feature isn't implemented.

Okay, I now it's really all down to you. I'll do what I can on it, but it's really you who has to do the vast majority of the work, so it's a bit of an imposition I'm making on you. But still, it would be great, we need it, and I know you can do it.

Pretty please!

JScones · 05-06-06, 08:51 AM

Quote:

Originally Posted by HEMISENT

The "ChooseFrom" is all that changes. The settings pretty much stay the same but the percentages dictated by the "ChooseFrom" line are what changes. eg 1939 setting x=15%, 1940 setting x=18% etc-(Does that make sense?)

Yes, thanks. I need to find a solution that balances flexibility with ease of use. I'll ponder it a bit...

Quote:

Originally Posted by HEMISENT

Question
using your lateral thinking theme from a few days ago-
Can I do this?
seperate actions using the same file.
*For testing purposes only*

[0_data\Library\Cameras.dat]
;Randomly adjusts blur duration time to simulate periscope seal/lens integrity,
FileType=B
ChooseFrom=8 ;50% chance-if Commander does not pick one will it move to the below files?
RndMidPat=1

0_x2ECD=20 ;Attack Periscope Drops duration[4]
0_x2EE2=20 ;Attack Periscope Blur duration[3]
1_x2ECD=37
1_x2EE2=37
2_x2ECD=60
2_x2EE2=60
3_x2ECD=3600
3_x2EE2=3600
;--------------------------------------------------------------------
[1_data\Library\Cameras.dat]
;Randomly disables attack scope zoom, simulates periscope magnification breakdown.

FileType=B
ChooseFrom=4 ;50% chance-if Commander does not pick one will it move to the below file?
RndMidPat=1

0_x302F=1.5
0_x304E=1.5
1_x302F=6.0
1_x304E=6.0
;--------------------------------------------------------------------
[2_data\Library\Cameras.dat]*this is a combination of the above two files*
;Randomly adjusts blur duration time and disables attack scope zoom to
simulate periscope seal/lens integrity combined with inoperative magnification

FileType=B
ChooseFrom=2
RndMidPat=1

0_x2ECD=20
0_x2EE2=20
0_x302F=1.5 ;Zoom
0_x304E=1.5 ;Zoom
1_x2ECD=20
1_x2EE2=20
1_x302F=6.0
1_x304E=6.0
;--------------------------------------------------------------------

Sabotage files have potential for numerous events all using the same file-mostly it's the NSS_U boatx.sim file. In the Random folder structure it works fine but using Randomized events.CFG I had problems with conflicting files shutting each other out. If the avove example will work then that solves my problem. If it will not work then I have to completely rewrite the Sabotage files in a format that is Randomized events.CFG friendly

Using your above example, [1_data\Library\Cameras.dat] will still run regardless of whether [0_data\Library\Cameras.dat] ran or not. Likewise [2_data\Library\Cameras.dat] to [1_data\Library\Cameras.dat].

But using the above example, the 0_ and 1_ sections are meaningless as the 2_ section will *always* result in a selection which will overwrite a 0_ or 1_ selection anyway.

But yes, you can build layers. It's prolly like building a house. Get the foundation down first, then add the different floors. Prolly not the best analogy, but you get the idea.

HEMISENT · 05-06-06, 08:52 AM

Hi Beery, Welcome back!
I like the idea of a patrol log too

.

To quote Beery "Pretty Please"

HEMISENT · 05-06-06, 08:54 AM

Also, while I'm on a roll what's the chances of incorporating SH3 Gen into Commander. I think it's really a neat feature.

JScones · 05-06-06, 09:02 AM

Quote:

Originally Posted by HEMISENT

Also, while I'm on a roll what's the chances of incorporating SH3 Gen into Commander. I think it's really a neat feature.

I did discuss it with GE a while back. But IIRC if wasn't considered feasible for various reasons.

HEMISENT · 05-06-06, 09:12 AM

Quote:

Originally Posted by JScones

[0_data\Library\Cameras.dat]
;Randomly adjusts blur duration time to simulate periscope seal/lens integrity,
FileType=B
ChooseFrom=8 ;50% chance-if Commander does not pick one will it move to the below files?
RndMidPat=1

0_x2ECD=20 ;Attack Periscope Drops duration[4]
0_x2EE2=20 ;Attack Periscope Blur duration[3]
1_x2ECD=37
1_x2EE2=37
2_x2ECD=60
2_x2EE2=60
3_x2ECD=3600
3_x2EE2=3600
;--------------------------------------------------------------------
[1_data\Library\Cameras.dat]
;Randomly disables attack scope zoom, simulates periscope magnification breakdown.

FileType=B
ChooseFrom=4 ;50% chance-if Commander does not pick one will it move to the below file?
RndMidPat=1

0_x302F=1.5
0_x304E=1.5
1_x302F=6.0
1_x304E=6.0
;--------------------------------------------------------------------
[2_data\Library\Cameras.dat]*this is a combination of the above two files*
;Randomly adjusts blur duration time and disables attack scope zoom to
simulate periscope seal/lens integrity combined with inoperative magnification

FileType=B
ChooseFrom=2
RndMidPat=1

0_x2ECD=20
0_x2EE2=20
0_x302F=1.5 ;Zoom
0_x304E=1.5 ;Zoom
1_x2ECD=20
1_x2EE2=20
1_x302F=6.0
1_x304E=6.0
;--------------------------------------------------------------------

Using your above example, [1_data\Library\Cameras.dat] will still run regardless of whether [0_data\Library\Cameras.dat] ran or not. Likewise [2_data\Library\Cameras.dat] to [1_data\Library\Cameras.dat].

But using the above example, the 0_ and 1_ sections are meaningless as the 2_ section will *always* result in a selection which will overwrite a 0_ or 1_ selection anyway.

But yes, you can build layers. It's prolly like building a house. Get the foundation down first, then add the different floors. Prolly not the best analogy, but you get the idea.

So, if I understand correctly with the above example Commander may choose to load 0_ and it may also choose to load 1_ but if it chooses to load 2_ that one will over ride the previous selection. because it's using the same file extension numbers from the tweaker?

JScones · 05-06-06, 09:15 AM

Quote:

Originally Posted by HEMISENT

So, if I understand correctly with the above example Commander may choose to load 0_ and it may also choose to load 1_ but if it chooses to load 2_ that one will over ride the previous selection. because it's using the same file extension numbers from the tweaker?

It *may* choose a setting from 0_. It then *may* choose a setting from 1_. It then *will* choose a setting from 2_ simply because you have two entries and ChooseFrom is set to 2. If ChooseFrom was set to 8, for example, then it *may* choose a setting from 2_. End result being that any, none, or all, of the blocks will "load".

GlobalExplorer · 05-06-06, 09:46 AM

Quote:

Originally Posted by HEMISENT

Also, while I'm on a roll what's the chances of incorporating SH3 Gen into Commander. I think it's really a neat feature.

As good as it sounds, apart from an option to start Sh3Gen directly from Sh3Cmdr, I never saw any real advantage.

Because even if Sh3Gen would be incorporated in Sh3Cmdr, you'd still have to save / alt-tab / reload, as you did with Sh3Gen stand alone. It would never be possible to write the intelligence update inbetween patrols, only mid-patrol. That's the fundamental difference between the two apps: One writes before/after the patrols starts/ends, the other one during patrol.

I am sometimes a bit slow thinking, so maybe you have an idea how the fusion could work, and what the benefit would be?

JScones had suggested command line options for Sh3Gen or other apps, and I think this doesn't sound a very complicated solution, something that could be added in the future .. I would be interested.

But so far the two apps can be run alongside w.o. problems, I haven't heard any complaints for months.

GE

P.S. Jaeson, I hope you are not leaving SHIII completely are you?

05-06-06, 06:45 AM	#1
JScones Navy Seal Join Date: Apr 2005 Posts: 5,501 Downloads: 19 Uploads: 0	OK, the LAST AND FINAL CALL for SH3Cmdr additions! I am close to finalising SH3Cmdr Release 2.6 - the final SH3Cmdr. So far the changes include: - Added ability to change crew officer faces (includes 3D head and hat wearing) - Crew transfer message now includes crewman's main qualification - Added ability to randomise main screen banner (banners by Beery, jcwolf, JonZ and Tikigod have been included) - Added new "Static settings" feature - 'FileType' parameter no longer required in "Randomised events.cfg" file - Added ability to generate randomised events by year ("Randomised events_1939.cfg" and so on) - Improved backup mechanism for files scene.dat and Basic.cfg I've also spent a fair bit of time cleaning up all the Cfg files to remove redundant data issues. Basically, I think I now have SH3Cmdr at a place where it can continue to evolve without the need for me to release updates. I have just a few more planned additions and it will be ready. SOOO...here is your LAST EVER chance to make suggestions for inclusions/corrections/whatever. Of course, I'll decide what's included based on complexity and time to implement, but if you don't ask...

05-06-06, 07:21 AM	#2
HEMISENT Ace of the Deep Join Date: Feb 2003 Location: Northern Illinois Posts: 1,052 Downloads: 135 Uploads: 0	Malfunction files ready to go. 1939-1945/7 seperate year Randomized events_19XX.CFG files completed/tested. Zipping up now. What about the Sabotage folders which are year/month specific? __________________ Nuke 'em till they glow!

05-06-06, 07:25 AM	#3
Salvadoreno Grey Wolf Join Date: May 2005 Posts: 887 Downloads: 119 Uploads: 0	add an overhaul feature. Where after about 3-6 patrols your boat is radomly selected for an overhaul and a few months go by ingame when u sail again. __________________

05-06-06, 07:51 AM	#5
HEMISENT Ace of the Deep Join Date: Feb 2003 Location: Northern Illinois Posts: 1,052 Downloads: 135 Uploads: 0	Jaesen Just E mailed the 7 Randomized Events_19XX.CFG files . I'll will work on the Sabotage numbers with their respective dates and percentages over the weekend and PM them to you hopefully by tomorrow night. If I get a chance I may be able to wrap up the malfunctions for Type II's also - I really would like to finish this whole thing and move on. I'm dying to play around with Gouldjg's Chaos files. __________________ Nuke 'em till they glow!

05-06-06, 08:48 AM	#8
Beery Admiral Join Date: Nov 2004 Location: Silver Spring, MD, USA (but still a Yorkshireman at heart - tha can allus tell a Yorkshireman...) Posts: 2,497 Downloads: 0 Uploads: 0	Hehe, I know you already know this Jaesen, but what the heck - one last chance to plug the Patrol Log feature. Please please pretty please - Patrol Log, Patrol Log, Patrol Log! After all, what's not to like - we'll get a real patrol log out of it for every mission, updated with the events as they happened. It's a way to relive our battles - to remember our greatest missions. Just imagine - you complete a patrol, fire up SH3 Commander, and you get to read an authentic log of events. You can see when you fired your first torpedo; you can see when the merchant finally sank. You'll see how many depth charge attacks you underwent, and how many times you saw enemy aircraft. It will even remind you of the weather conditions - all of this without having to scroll through the repetetive and useless info of the game's patrol log data files. Even after a year you'll be able to go back and look at your favourite commander's logs and say "Oh yeah, I remember that patrol. That was the best patrol" and you'll see exactly what made the patrol so amazing. Things you had forgotten will come flooding back as you read through the log's timeline. You'll gaze in wonder as you find that you survived 50 depth charge attacks. Man, that would be awesome. You already know the greatness of the Commander history feature - probably one of the top three features of SH3 Commander. I'm certain that a working patrol log will also be among the top five, since, like the Commander history feature, it creates a story from our games. This is a feature we've already spent time developing. You've already thought out the mechanics of it, and I've filled out (as best I could) the patrol.log text file based on your instructions. Please say you'll complete it. We know it can be done, we know it would make SH3 Commander even better. Don't let fatigue get the better of us. Think of it like this - we've been under severe depth charge attacks. We're stuck on the bottom, we've been working for 24 hours straight to save the boat. One last effort at the pumps will get the ship rising to the surface before we're out of air. Let's make that final effort and take our boat home! I realise that it's mostly my fault that this feature hasn't already been done. You put the ball in my court on this issue and I dropped it, and when I picked it up again the game was nearly over. If I hadn't lost the will to mod during the last few months, this thing would probably be done already. I wish I could go back and change things, but I can't. All I can say is that I know I'll regret it if this feature isn't implemented. Okay, I now it's really all down to you. I'll do what I can on it, but it's really you who has to do the vast majority of the work, so it's a bit of an imposition I'm making on you. But still, it would be great, we need it, and I know you can do it. Pretty please! __________________ "More mysterious. Yeah. I'll just try to think, 'Where the hell's the whiskey?'" - Bob Harris, Lost in Translation. "Anyrooad up, ah'll si thi" - Missen.

05-06-06, 08:04 AM	#6
JScones Navy Seal Join Date: Apr 2005 Posts: 5,501 Downloads: 19 Uploads: 0	@Hemisent. Wow, you have been busy! What it says to me is that the way I had planned to build the malfunctions feature won't work because it would be too linear. So, can you pls just confirm for me exactly what you want to be able to change month by month within each year? Is it just the "ChooseFrom" probability aspect (ie 20% chance between Jan and May then 50% between Jun and Dec)? Or the settings as well (Crash depth set to 100m between Jan and May and 150 between Jun and Dec)? I suspect the former, which if so should just require a minor adjustment to the current Randomised events file. But pls let me know if it's the latter too. I have two potential solutions in mind at the moment, one revolving around "ChooseFrom" and one being the addition of a new optional paramater "ApplyToMonths". BTW, how did you find using the Randomised events feature? Any comments or feedback?

05-06-06, 08:52 AM	#10
HEMISENT Ace of the Deep Join Date: Feb 2003 Location: Northern Illinois Posts: 1,052 Downloads: 135 Uploads: 0	Hi Beery, Welcome back! I like the idea of a patrol log too . To quote Beery "Pretty Please" __________________ Nuke 'em till they glow!

05-06-06, 08:54 AM	#11
HEMISENT Ace of the Deep Join Date: Feb 2003 Location: Northern Illinois Posts: 1,052 Downloads: 135 Uploads: 0	Also, while I'm on a roll what's the chances of incorporating SH3 Gen into Commander. I think it's really a neat feature. __________________ Nuke 'em till they glow!