HentHighSchool Development Forum

Will be adding notes on "fitting into" the current system here... so this is just placeholder post for now...

So... Current things that would be good to have done:

1 Pixel Up Issue
I have managed to ID how and where to solve the 1 pixel up problem... but requires someone with php skills to implement properly.

Line 285 in lib.php is:
   imagecopy($dstimg, $srcimg, $targetXPosition, 0, $deltaX, 30, $charaXSize, 1121);

By changing to:
   imagecopy($dstimg, $srcimg, $targetXPosition, 0, $deltaX, 29, $charaXSize, 1121);
the chars are shift down 1 pixel... so almost fixed... but:
•   This solves the problem for Adult females only
•   For Adult Males the value has to be 32, and for Students, the value has to be 30

So... can set to 29, 30 or 32, depending on what you're working on.
But... It would obviously be much neater if the php check the file name and switched the value accordingly.
EDIT: I have edited lib.php and it now supports the above (will include on v2 of the bundle)

Folder Structure
I think the current folder structure can be improved to make things easier to navigate.

If you have downloaded the bundle above, you will see:
•   I have put .bat 'launchers' into the top folder level, and the default .txt files in a separate sub-folder at this level (HHS+ Default People).
•   The idea is make using this easier and not to have to go into (and potential break) the Kisekae/KKKL Stuff

In the same way, it would be easier to work with and navigate if the "SourceFiles" was renamed "HHS+ Work in Progress" (or maybe "HH+ WIP Files") and placed at the top level.
Likewise, the images folder could be renamed "HHS+ PD Images" and also placed at the top level.

Adding Pubic Hairs (the big one?)
Currently, I add all the Pubic hairs to the images using a separate Image editor. There are 17 variants of Pubic hair and this a time consuming process.
(and has to done for each new outfit added)

As the Autocutter/Batch Image Maker is obviously modding the .txt files on the fly to produce all the breast sizes etc.
It would seem at least feasible that the pubic hairs could be added on the fly...?

Obviously, that would mean crafting the .txt elements (i.e. create .txt files with all the pubic hairs and extract the relevant bits).
So I could do that… but the php stuff is not really my skill set.


Any help with any of the above would be very much appreciated... 

Quote from: Spinner on November 30, 2016, 12:15:00 am

1 Pixel Up Issue

will be done..

... Wow... ty... 

Quote from: Spinner on November 30, 2016, 12:15:00 am

Folder Structure
In the same way, it would be easier to work with and navigate if the "SourceFiles" was renamed "HHS+ Work in Progress" (or maybe "HH+ WIP Files") and placed at the top level.
Likewise, the images folder could be renamed "HHS+ PD Images" and also placed at the top level.

I'll make both configurable so you can tweak config.php when you make your bundle.. you could simply set it to "../HHS+ Work in Progress".. i prefer not to make it the default, cause then the cutter would have a depedency on directories above its own, complicating testing and updating

Also wow... 

Quote from: Spinner on November 30, 2016, 12:15:00 am

Adding Pubic Hairs (the big one?)
Currently, I add all the Pubic hairs to the images using a separate Image editor. There are 17 variants of Pubic hair and this a time consuming process.
(and has to done for each new outfit added)

As the Autocutter/Batch Image Maker is obviously modding the .txt files on the fly to produce all the breast sizes etc.
It would seem at least feasible that the pubic hairs could be added on the fly...?

Obviously, that would mean crafting the .txt elements (i.e. create .txt files with all the pubic hairs and extract the relevant bits).
So I could do that… but the php stuff is not really my skill set.

I'd need some more info about how public hair is added to PDs..
Does the current PD system support a "Public Hair" directory containing the different public hair overlays? Or do you simply take the different variations of public hair and generate different versions of each body with different public hair? Or maybe only for the last body? The last two? Or only for bodies in which public hair is already visible?
Assuming you create different variations of the bodies, how does this affect naming since i understand the current PD system expects all bodies to be named "Gender_nbr.png"? (E.g. would we then have a "Female_0_ph00.png", "Female_0_ph01.png", etc..?)

I'm pretty sure this could be automated, but i'd need to know more about what goes in and what comes out

Yeas... so I have a folder structure... and there are details to be worked out... (i.e linking thinking)

But I can confirm that the notion works... I have tested and have identified the "bits" of the .txt files required can be isolated, extracted and placed into the .txt file to produce the outcome.

Will put together full details as soon as practical... 

New bundle (v2.1) posted... Has Anaconda's latest changes... 

That would be just fine for the generic characters.  Keep in mind that some won't need back heads, though.  For special characters, I've been doing it like this:

Let's use the female principle as an example.  She has three different back heads, and several different front heads.

It would be Principal_FHead_Back_01.png, Principal_FHead_Back_02.png, Principal_FHead_Back_03.png, Principal_FHead_Front_01.png, Principal_FHead_Front_02.png, Principal_FHead_Front_03.png, Principal_FHead_Front_04.png, etc.

That would be just fine for the generic characters.  Keep in mind that some won't need back heads, though.  For special characters, I've been doing it like this:

Let's use the female principle as an example.  She has three different back heads, and several different front heads.

It would be Principal_FHead_Back_01.png, Principal_FHead_Back_02.png, Principal_FHead_Back_03.png, Principal_FHead_Front_01.png, Principal_FHead_Front_02.png, Principal_FHead_Front_03.png, Principal_FHead_Front_04.png, etc.

Yeah... the nomenclature defined is aimed at suiting most uses...

Nomenclature for special people is better retained as hand crafted (i.e. manually renaming the files).  Reasoning:
o  Cutting code to handle each specific takes as long (or longer) than simply renaming the files.
o  If also adds complexity to both the code and .txt file naming convention. And adding complexity, increases the chance of bugs and human error.
o  As these are rarely changed, it doesn't make sense to add that overhead.

Hey Anaconda,

So.. have done the work re the pubic hairs.
Took a bit 'cause either Kisekae has changed or some our existing stuff was hand crafted (so had to go through a color matching exercise)

So here is how it works:
o  The Kisekae .txt define pubic hair at 'eh_' (with no pubic hair = just 'eh_').
o  So, for each hair type, the 'eh_' needs to switched to ehX.nnnnnnn (where X is the style and nnnnnnn is the Hex color code).
    NB: If one of the 'standard' colors is used, nnnnnnn become simply nn, where it is the Kisekae color pallet index.
          However, I have deliberately avoided that, to mitigate the possibility of indexes being changed in Kisekae.

o  We currently use 17 pubic hairs states (16 with hair and one shaved)... for Female Adults only.
    I intended to add hair for adult males, but it is a lot of work, and no-one asked for it.
    If this all goes to plan though, doing that could potentially become a lot easier.

o  Below are the names and 'eh_' code for each of the 17 hair states:

Folder structure
o  The structure follows the same nomenclature as the hairs. E.g. Black_Tuft is the folder name for hair 'Black_Tuft'

o  Creating each variant is the same as creating just one... everything for goes to each sub-folder.
    Due to the mechanics of the current PD display code, that includes breasts.

o  A nice to have would be to not include the heads (but deleting those manually is no major effort). 

o  Obviously pubic hair will not be visible for all outfits.  In fact, just a few (6, 7 and/or 8, depending on the outfit).
    But, deleting the unwanted ones is also no big effort (compared to building all this in an image editor).
    And your new feature, of being able to "hide any chars", almost solves that...

Hide any chars feature
o  This new feature of yours, turned out to be real boon in time-savings when I did all the work to make the pubic hair .txt bits.

o  One drawback though is that the feature currently names the file for the first char found as 0, then 1, etc.
    The main benefit of this feature is as I described in the opening post for v2.1 (i.e. speed up editing) and to support this kind of thing.
    In order for it to do either of these though, the file names need to match the char position, even when hidden.

o  Obviously .txt structure allows for this...  So, if at all possible, doing that would be superb...