Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Fri, Dec 22, 2023 06:37 PM UTC in reply to François Houdebert from 09:27 AM:

I think shades like those on the wings are caused by the normalmap. But I thought I had made that completely neutral too. As I made them by hand I might have mesed up, and the mapping to the uvs might not be continuous.

Anyway, I just arrived at the bottom of the learning curve, and in a few days I can probably do much better. E.g. the wings now are razor sharp, which makes them invisible when viewed edge on. (You would still see the other, but it still looks unnatural.) This can be avoided by not making them completely planar, and give them a thickness. (The need two sides anyway, as all surfaces act like one-way mirrors.)

I have created some 3d pieces with the piece-creation tool I am developing. It can now also make elliptic and excentric levels. (But still all strictly horizontal.) This increases the possibilities. It also creates the maps, as uncompressed Windows BMP files. (But with the Linux command 'convert'  I can then turn them into JPG. On Windows I would do that with MS Paint.)

At the moment it still creates a completely neutral normalmap, and it uses false colors (red, green and blue) for the diffusemap. Teese colors alternate between horizontal sections of the piece, so that you can use a drawing program to fill them with the desired colors. With a sufficiently advanced drawing program you might even create smooth color gradient. (But I don't seem to have such a program; GIMP is either very primitive or I don't know how to use it.) Of course the generation tool could very easily create the color gradients, if it only knew what colors to use.

I suppose we could derive a mapping tilt-ange to color from the existing Jocly pieces, and then let the program smoothen those with a gradient when the angle between neighboring surfaces is small (but keep discontinuous jumps when the angle becomes acute). The same way it should do it for the normalmap.

I made some new pieces, which I intend to use for the Shogi generals and the Omega Champion. I currently replaced the N, B and Q of the Staunton set with those ( http://hgm.nubati.net/jocly/jocly-master/examples/browser/control.html?game=classic-chess ). With a little improvement of the maps I think they would be very acceptable. I still intend to paint stars on the caps of the generals to better distinguish those from each other.

As for the Phoenix: I am quite satisfied depicting the Phoenix as a Stork. (After all, it was a mythical bird, so no one knows exactly how it looked. But it was not a bird of prey, so it would not have looked like an Eagle!) Like I already do in 3d (even though the Stork there still needs some work). I would try to match that in the 2d graphic. Even if it means I have to draw it myself. Using an Elephant for Phoenix strikes me as horrid. For the Kirin I am quite happy with the Giraffe, which is good quality both in 3d and 2d. (And in 3d it is about equally tall as my Stork, which is also nice.)

I am not sure if the representation has to be constant over games. In Makromachy I used the Bow for the Phoenix, because that fits with the theme of the flying pieces. I can always use the excuse there that it is not a normal Phoenix, as it blocks flying pieces, onlike any other normal piece.


Edit Form

Comment on the page Jocly

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.