Announcing the OOTP Uniform Maker

[tehsuigi]

Sure thing! The font loads successfully the first time, and does work, but second time breaks.Thanks, Eriq!

[eriqjaffe]

Ohhhh, I see what's happening. Once a font is loaded it becomes available to all three uniform elements - if you load it for the jersey, it gets added to the drop-down menu for the cap and pants automatically, there's no need to load it separately for each element - and, indeed, you can't. It doesn't stop you from still using the font that's already loaded, it just throws that nebulous error message.

I don't think it ever occurred to me to try loading the same font multiple times so I never saw it.

[tehsuigi]

I'm still running into the "font loading failed undefined" error if I've loaded the font once before on a previous uniform, and it's not in the drop-down menu for any of the three uniforms.

Here's my repro steps.
1. Start a new uniform in OOTP uniform maker.
2. Load the local font.
3. Save the uniform file, and close the uniform maker.
4. Re-open the uniform maker, and try to load the local font from before in again - fails.

The font is also unavailable in the drop-down after you close the uniform maker.

[eriqjaffe]

Originally Posted by tehsuigi

Here's my repro steps.
1. Start a new uniform in OOTP uniform maker.
2. Load the local font.
3. Save the uniform file, and close the uniform maker.
4. Re-open the uniform maker, and try to load the local font from before in again - fails.

Are you re-loading the uniform before you try to load the local font? Because the font gets encoded into the .uni file and should come back automatically when you reload a uniform.

Originally Posted by tehsuigi

The font is also unavailable in the drop-down after you close the uniform maker.

That is normal and expected behavior - custom fonts aren't permanently added to the app.

[tehsuigi]

Originally Posted by eriqjaffe

Are you re-loading the uniform before you try to load the local font? Because the font gets encoded into the .uni file and should come back automatically when you reload a uniform.

No, this would be with a completely blank uniform that I want to use the same font for. The uniform file is not loaded, but I still get the error.

[eriqjaffe]

Originally Posted by tehsuigi

No, this would be with a completely blank uniform that I want to use the same font for. The uniform file is not loaded, but I still get the error.

Interesting. I'll see if I can figure that out.

[ProXy]

Hey eriqjaffe, how big should the custom layer be? Or even, how exactly do custom layers work? I'm trying to create a jersey with a custom zigzag pattern outlining the sleeves, bottom trimming, the sides, etc. and I'm not sure why just taking a screenshot of the jersey file and tracing the pattern around it fails to position the elements properly.

As an example of what I'm trying to do, here's a picture of what I'm working on (or well, a simplified version, since it's just the collar). I'm trying to center the triangle pattern around the collar. For whatever reason, using the jersey file as a template doesn't seem to automatically get the placement correctly. I don't know if this is because the custom layers assume a particular file size that is different from the jersey file size or if there's some particular other way the custom layers work to arrange objects in them on the jerseys or something else entirely.

[spleen1015]

Hi eriq, updated my copy of your app tonight and noticed not a lot of vintage options. Just wondering if they'll ever be added, things like the different ties, neckware, the breast shields & panels.

I really appreciate all of your hard work on this.

Thanks.

[eriqjaffe]

Originally Posted by ProXy

Hey eriqjaffe, how big should the custom layer be? Or even, how exactly do custom layers work?

Custom layers should theoretically be the same size as the uniform element - 512x1024 for the jersey and 512x512 for the cap and pants.

Be aware that the jersey you can see in the app is not actually full size - the viewport is scaled down to 75% so everything will fit on screen, so just taking a screenshot won't work, although upscaling a screenshot should work as a rough template.

That being said you can import a custom layer of any size and there is code that tries to scale custom layers which doesn't seem to work properly - you can see that even importing custom layer that is too small winds up scaling it incorectly. I've actually been working on some uniforms for a solo league and been running into that very issue. I expect to have an update out within the next day or two that will fix (or at least work around) the issue.

Originally Posted by spleen1015

Hi eriq, updated my copy of your app tonight and noticed not a lot of vintage options. Just wondering if they'll ever be added, things like the different ties, neckware, the breast shields & panels.

Maaaaaybe? I've tried bringing in some of the vintage elements and the way the new model splits elements around the neckline has proven frustrating. I'm not saying never, but...not yet.

[spleen1015]

Originally Posted by eriqjaffe

Custom layers should theoretically be the same size as the uniform element - 512x1024 for the jersey and 512x512 for the cap and pants.

Be aware that the jersey you can see in the app is not actually full size - the viewport is scaled down to 75% so everything will fit on screen, so just taking a screenshot won't work, although upscaling a screenshot should work as a rough template.

That being said you can import a custom layer of any size and there is code that tries to scale custom layers which doesn't seem to work properly - you can see that even importing custom layer that is too small winds up scaling it incorectly. I've actually been working on some uniforms for a solo league and been running into that very issue. I expect to have an update out within the next day or two that will fix (or at least work around) the issue.

Maaaaaybe? I've tried bringing in some of the vintage elements and the way the new model splits elements around the neckline has proven frustrating. I'm not saying never, but...not yet.

Thanks, man!

[eriqjaffe]

Version 0.7.2 has been released!

What's New

• Added "Adidas" shoulder stripes to the jersey.
• Changed the white "Adidas" pants stripe to transparent by default.
• Added a link to fabric.js to the "About" menu to give credit where credit is due.

What's Fixed

• The code that scales a custom jersey layer has been removed, it was incorrectly scaling images and I haven't been able to figure out why. So now they'll just import at their native size.

https://github.com/eriqjaffe/OOTP-Un...ases/tag/0.7.2

[kq76]

Eriq, do you realize you have Beaverton (aka Nike Script) labeled as Fancy Block? I realized because I like it and went to find it, but all I could find was the other Fancy Block which doesn't look anything like it.

I'm impressed with the variety you came up with by the way. My tastes are too narrow. I would have had like a dozen Garalde, a few Scripts, a few Slabs, and flat out randoms of the other types. I could see a lot of yours working out just right for different people.

[MattD1972]

I was a latecomer to 23, but I love redoing all of the uniforms on this, as the PSD template only works as a texture layer here and the old uniforms still work...if you want backwards patches and odd things duplicating at the bottom of the jersey. Anyway, I'm running into an issue with wordmarks/names. When I try to do any arched/radial arched names, the game goes into the red spinning screen (loading/canceling clears that). This became a particular problem after going to version 0.7.2. Do you think that doing a dump/reinstall of both the maker and ImageMaiick will get it working again?

[tigiras]

Why doesn't the program create uniform files. It only creates a file without any file extension. What am I doing wrong, please?

[eriqjaffe]

Originally Posted by MattD1972

When I try to do any arched/radial arched names, the game goes into the red spinning screen (loading/canceling clears that). This became a particular problem after going to version 0.7.2. Do you think that doing a dump/reinstall of both the maker and ImageMaiick will get it working again?

The ImageMagick executables have to be in the system path tow work - you can check that by opening up a command prompt and just running "magick". If you get a message that "magick is not recognized as an internal or external command" that means it's not in the path. Reinstalling ImageMagick shoud fix that.

Originally Posted by tigiras

Why doesn't the program create uniform files. It only creates a file without any file extension. What am I doing wrong, please?

Uniforms are created as ZIP files. Windows doesn't display "known" extensions by default, but other than that I have no idea because the filenames are very specifically set in the app.

[Deft]

eriqjaffe, are you planning a refresh of your mod with the OOTP24 release? Are you open for more potential options to put into the next version?

[eriqjaffe]

INITIAL RELEASE FOR OOTP 24



As you might expect, most of the changes revolve around OOTP24's new name and number fonts.

What's new?

• Name & number fonts for jerseys compatible with OOTP 24.
• A dedicated user fonts folder - just drop .ttf/.otf files in there and they will automatically be imported into the Uniform Maker.
• Custom fonts, as long as they are in the user fonts folder, can be set as default fonts for the various uniform elements.
• A "Team Display Colors" section has been added to the Jersey tab. This will let you set text and background colors for your teams - please note that OOTP currently uses the "background color" as the the "high sock" color.
• A few more "Varsity" font variants are now included with the app.
• An importable XML file is included in the zip file.

What's changed?

• The "player name and number" section has been removed from the Jersey tab.
• The "number" section has been removed from the Pants tab.
• Cap eyelets now default to "grouped" since probably 90% of the time they'll be the same color anyways.
• The library that generates the font drop-downs has been changed to make them easier to manage.
• The font rendering library has been shifted to opentype.js in order to better handle the font bounding boxes.
• "Vertical" and "Diagonal" jersey wordmarks no longer rely on ImageMagick, but ImageMagick is still required for full functionality.

https://github.com/eriqjaffe/OOTP-Un...ses/tag/v0.8.2

[pstrickert]

Brilliant! Thanks, Eriq!

[Deft]

Wonderful!

[zappa1]

Yeah like what everybody is saying this is really great.