Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Wed, Apr 24 08:33 AM UTC in reply to A. M. DeWitt from Tue Apr 23 08:34 PM:

There appears to be a mismatch between the shogi graphics on CVP and that in the current source code. On CVP there are directories .../chessbase/res/shogi and .../chessbase/res/shogi2. The first contains the tile meshes and diffusemap for mini-Shogi, the second for Chu and Tenjiku Shogi. The current source code was derived from the latter, even though it reorganized the location where the diffusemaps are stored.

The problem occurs because the newly made Seireigi diffusemaps are made according to the Tenjiku design, (and placed so the view files can find them), but use the mini-Shogi tile mesh files. And it appears that these mesh files specify the use of a different part of the diffusemap for painting the top face: the mini-Shogi tiles use the top-left quarter, while the Chu-Shogi tiles use the bottom-left quarter of the maps.

I fixed the problem by editing the chu-seireigi-view.js file, to make it use the mesh files from the shogi2 folder. The kanji then appear. But apparently not all mesh files used by seireigi are there, as some of the pieces now disappear completely.

[Edit] The problem was in the map files: some Seireigi pieces use the diffusemap of Chu-Shogi pieces, and these are in a different location on CVP from where they are in the current source code (and have different filenames too). I adapted the path for the diffusemaps of Copper, Kirin, Phoenix, Lion and Queen to where these images are on CVP, and now the initial position of Chu Seireigi is correctly displayed.


Edit Form

Comment on the page Play Chess Variants with 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.
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.