Tutorial: simple journals and Linking Books

[Deledrius]

I also noticed that none of the pythons from the moul-scripts-master of the H-uru/moul-scripts GitHub show up in the drop down menu

They show up for me. What version of the plugin are you using?

[Karkadann]

Im using the original Cyan plugins,
If I recall correctly their was something about no glue or id # might cause a python to not show up in Max and the github files don't have the python glue added to each file

[Deledrius]

Im using the original Cyan plugins,
If I recall correctly their was something about no glue or id # might cause a python to not show up in Max and the github files don't have the python glue added to each file

Yeah, we cleaned up the Python to be less of a mess (and we're still working on making it even better ). That plugin bug was fixed a long time ago.

[Karkadann]

Ok a few more questions
what version of Max do the fixed plug-ins work with, and how can I get the journal to read a picture file other then an hsm file or how to I convert a jpg or a png to an hsm file

[Sirius]

How can I get the journal to read a picture file other then an hsm file or how to I convert a jpg or a png to an hsm file

Sorry, it seems I didn't cover this in the tutorial.
All you need to do is put the texture on some object in the world (preferrably hidden, it doesn't even need a face or uv mapping). The plugin should automatically convert it to the right format.

About the name you must put in the <img scr> thing, it should be the name of the image file you're using, minus the extension, followed by something like *0#0.hsm. Sounds crazy ? Yeah, that's Max naming convention.
So if you have a texture named "mytexture.png", the name in the img tag should be src="mytexture*0#0.hsm". Sometimes it might be "mytexture*0#1.hsm", or "mytexture*0#2.hsm" (I couldn't say why).
The best way to be sure is open dat/<YourAge>_district_Textures.prp in PRPShop, and check the name of the corresponding image file.

Blender users don't need to worry about this, the name they must use is the texture name in Blender, ie: the name in the "IM" field of Blender, next to the "Reload" button.

[Karkadann]

Is their something else im missing? Ive tried jpg, png, dds, I got the right *0#0.hsm" info from prp shop I tried exporting the image from prp shop, I tried resizing it smaller thinking it might be to big.


CALGON TAKE ME AWAY

It does read the black swirly thing it just will not read the image I put into it

[Deledrius]

Ok a few more questions
what version of Max do the fixed plug-ins work with

I know it works with Max 7, and at least up to 2012. Pretty sure it works with versions between, but if you run into trouble, let us know.

About the name you must put in the <img scr> thing, it should be the name of the image file you're using, minus the extension, followed by something like *0#0.hsm. Sounds crazy ? Yeah, that's Max naming convention.
So if you have a texture named "mytexture.png", the name in the img tag should be src="mytexture*0#0.hsm". Sometimes it might be "mytexture*0#1.hsm", or "mytexture*0#2.hsm" (I couldn't say why).
The best way to be sure is open dat/<YourAge>_district_Textures.prp in PRPShop, and check the name of the corresponding image file.

Blender users don't need to worry about this, the name they must use is the texture name in Blender, ie: the name in the "IM" field of Blender, next to the "Reload" button.

Technically, it's not a 3DS Max convention, but specific to the Plasma plugin. According to plBitmapCreator, the filename takes the form of:
name*flags#clipID@mixmethod&dropoffStart&dropoffStop&maxDetail&minDetail in order to normalize the names. The authors of PyPRP didn't have the same needs, and so did not do this. It's not really meant to be human-readable, just make sure that the same image with the same settings all end up with the same name and thus only stored and patched once.

[Sirius]

According to plBitmapCreator, the filename takes the form of:
name*flags#clipID@mixmethod&dropoffStart&dropoffStop&maxDetail&minDetail in order to normalize the names.

Of course ! That's obvious, I should have guessed

...

Just kidding !
It does create insane filenames, though... For instance:
islmcanvasdetail*0#0@mu&0.00&1.00&1.00&0.20.hsm

Is their something else im missing? Ive tried jpg, png, dds, I got the right *0#0.hsm" info from prp shop I tried exporting the image from prp shop, I tried resizing it smaller thinking it might be to big.


CALGON TAKE ME AWAY

It does read the black swirly thing it just will not read the image I put into it

If you can upload the data files you get once exporting, I can have a look at it (all I need is the book and clickregion prp, the texture prp and journal text file).

[Deledrius]

According to plBitmapCreator, the filename takes the form of:
name*flags#clipID@mixmethod&dropoffStart&dropoffStop&maxDetail&minDetail in order to normalize the names.

Of course ! That's obvious, I should have guessed

...

Just kidding !
It does create insane filenames, though... For instance:
islmcanvasdetail*0#0@mu&0.00&1.00&1.00&0.20.hsm

I was surprised to see what that insane mess meant myself, so I figured it might be funny/useful to others too.

[Karkadann]

If you can upload the data files you get once exporting, I can have a look at it (all I need is the book and clickregion prp, the texture prp and journal text file).

Im assuming the book and clickregion.prp are someplace in the Mainroom.prp?
so here are the Mainroom.prp, texture.prp, and the journal text file.


Thanks