Moondust Project thread [Support moved]

[Wohlstand]

Just asking, when did you changed the program name? IIRC it was "Platformer Game Editor" before, but yea I like the current name. Should I call it MP or something? hehe

Yes, since the recent time the project is "Moondust Project". The whole time the "PGE" was a codename, and it wasn't suitable for release name because of many namesakes and it's too common, so, the community poll did the choice to rebrand into "Moondust". And yes, Editor is not the only component of the project, its main part is the runtime engine, and Editor is a part of Moondust Devkit (it includes Editor, Calibrator, Maintainer, MusPlay, set of console helper tools, etc.).

So,

• The whole set of tools including the engine is called the "Moondust Project"
• Each component called "Moondust Engine", "Moondust Editor", "Moondust Maintainer", "Moondust Music Player", "Moondust Character Calibrator", "GIFs2PNG", "PNG2GIFs", "LazyFixTool", "Pallete Filter"
• The runtime part is called "Moondust Runtime Engine" or just "Moondust Engine"
• The all set of tools but Engine called "Moondust Devkit" (the toolkit used to develop levels, worlds, episodes, and related content)

Also, since December 2019 I stopped actively working on the X2 side, and Moondust Project is going to be developed fully independently. Mainly because X2 side tasks were contrasting with the main focus of the project and additionally caused the semi-hiatus at Moondust Engine development. So, there is a set plan to start the huge reconstruction of everything after the nearest stable release of the kit (there are Calibrator and Maintainer-side tweaks were left). Mainly, to get rid of the 2014ish code with a lot of architectural mistakes was done and not been resolved for a while.

[BlueStag]

Out of pure curiosity, will 32X music be supported? Knuckles Chaotix sounds weird with missing instruments.

[Wohlstand]

Out of pure curiosity, will 32X music be supported? Knuckles Chaotix sounds weird with missing instruments.

If you give me some examples, I will need to get a shot somewhere to extend GME library side.

Currently, VGM support lacks many chips and lacks the samples database support, so, in most, Sega Master System, Sega Megadrive ripd and libOPNMIDI's MIDI2VGM-converted songs were working here. There is parallel experiment to try out the libVGM thing, however, it lacks many important cases that reduces functionality support (for example, you will lose an ability to mute/unmute selected channels and broken tempo change support), so, until these cases will be solved, I can't take libVGM for the use. Also, there is a conflict with some part of libOPNMIDI that I will need to fix.

P.S. Any updates of MixerX won't appear at X2, because I don't actively participate the X2 project since December 2019.

So, my recent updates that X2 lacks:
- multi-music API (Allows crossfade and parallel cheap streams)
- updated NSF support (now there are all known chips supported, without this update, several NSF files will play silence or missing tracks)
- better support of stream/music cusrom effects (you can attach any custom FX, like echo, reverb, filter, etc. to individual music stream or to the whole output).
- ability to mute echo of SPC files
- ability to disable automatic arpeggio at libADLMIDI and libOPNMIDI, and, ability to supply custom WOPL/WOPN banks (feature needs macros support at engine side, that wasn't done at X2 and 38A at all. Moondust and TheXTech actually adds that)
- FluidSynth support with ability to supply custom SF2 files (same needs for macros support at game side)
- a bunch of bugfixes
- etc.

[Alucard648]

Site engine.wohlnet.ru is down. "Virtual server does not exist..."

[Wohlstand]

Site engine.wohlnet.ru is down. "Virtual server does not exist..."

Ouch, possibly a small mess at the server-side lemme fix that...

Added in 4 minutes 46 seconds:
Done, should work fine. Also, the engine-wohlnet-ru redirect works on plain HTTP only, for SSL I will need to tweak the web server's config for this host too.

EDIT: Done

[KnownStranger]

I have some questions:
1. Why the backgrounds with custom gfx have a star (*) in their name?
2. I made a txt file for a parallax background, when I tested the level an error message that I didn't get it appeared and I had to spend 15 minutes figuring out were I went wrong. In the end, I realized that I typed this: "[fill-color=0x000000]"(those square brackets were the problem). Wouldn't be a good idea to put in those error messages something like: "Check the txt file; you may have mistyped something."?

[deice]

1. Why the backgrounds with custom gfx have a star (*) in their name?
2. I made a txt file for a parallax background, when I tested the level an error message that I didn't get it appeared and I had to spend 15 minutes figuring out were I went wrong. In the end, I realized that I typed this: "[fill-color=0x000000]"(those square brackets were the problem). Wouldn't be a good idea to put in those error messages something like: "Check the txt file; you may have mistyped something."?

1. i believe it's just to signify that it's been modified.
2. that's because you actually didn't mistype anything. by putting brackets around it, all you've done is create a new background layer with the name "fill-color=0x000000" (i believe almost any character is legal there), so the game thinks it's just another layer and probably gives you an error about no image file being defined for it.

[Wohlstand]

I have some questions:
1. Why the backgrounds with custom gfx have a star (*) in their name?
2. I made a txt file for a parallax background, when I tested the level an error message that I didn't get it appeared and I had to spend 15 minutes figuring out were I went wrong. In the end, I realized that I typed this: "[fill-color=0x000000]"(those square brackets were the problem). Wouldn't be a good idea to put in those error messages something like: "Check the txt file; you may have mistyped something."?

1. This asterisk is a mark that shows the fact that listed background was customised, basically just a little help to visually quicker find your custom background rather than checking every one of them.
2. deice already replied. From my side: You better learn the valid INI syntax while composing your configs:

Code: Select all

; Comments starting from semicolons
[Section]    ; At backgrounds, the section name is always a line with a word inside brackets [], 
             ; except of [General] and [background2] sections are reserved for the header section for global setup.
key1 = value1   ; One of settings
key2 = value2   ; Another setting
key3 = value3   ; Third setting

The "fill-color" setting appears to be a setting of the global setup header (i.e. [General] or [background2], both names mean the same section. Also, orphan parameters (placed without section name) at the top of the file are treated as "[background2]" section by default).

[KnownStranger]

Thanks for answering my questions and for understanding the second question , but I have other "issue". Looks like the custom graphics that should have other appearance in the editor (example block-751e.png) don't work. Idk if this is happening only on my PC.

[deice]

Thanks for answering my questions and for understanding the second question , but I have other "issue". Looks like the custom graphics that should have other appearance in the editor (example block-751e.png) don't work. Idk if this is happening only on my PC.

that feature doesn't automatically work for all items. you should create a file in your level folder called "block-751.ini" and inside it put:

Code: Select all

image="block-751e.png"

[KnownStranger]

that feature doesn't automatically work for all items. you should create a file in your level folder called "block-751.ini" and inside it put:

Code: Select all

image="block-751e.png"

I thought that feature works automatically. At least the way to fix it is simple.

[apparition27]

Moondust Editor crashed on me for "Signal Segmentation Violation [SIGSEGV]".
I got the report:

Code: Select all

We're sorry, but Moondust Editor has crashed. 
Reason: Signal Segmentation Violation [SIGSEGV]


================================================
            Additional information:
================================================
Platformer Game Engine - Editor version: 0.3.2.2-beta
Architecture: x86_64 (64-bit)
GIT Revision code: 68a78df
GIT branch: stable
Build date: Nov 22 2022 12:47:05
================================================
Qt 5.14.2
SDL2 2.23.1
SDL Mixer X 2.6.0
================================================
 Please send this log file to the developers by one of ways:
 - Via contact form:          https://wohlsoft.ru/contacts/
 - Official forums:           https://wohlsoft.ru/forum/
 - Make issue at GitHub repo: https://github.com/WohlSoft/PGE-Project

================================================


0   Moondust Editor                     0x0000000102f231a4 _ZN12CrashHandler13getStacktraceEv + 68
1   Moondust Editor                     0x0000000102f24443 _ZN12CrashHandler23doCrashScreenAndCleanupE7QString + 131
2   Moondust Editor                     0x0000000102f2492e _ZN12CrashHandler13crashBySIGNALEi + 558
3   libsystem_platform.dylib            0x00007ff81ddcbc1d _sigtramp + 29
4   ???                                 0x0000000000000001 0x0 + 1
5   Moondust Editor                     0x0000000104366c2d _ZL16indexesFromRangeI5QListI11QModelIndexEEvRK19QItemSelectionRangeRT_ + 445
6   ???                                 0x0000000000000003 0x0 + 3

[Wohlstand]

Moondust Editor crashed on me for "Signal Segmentation Violation [SIGSEGV]".
I got the report:

Code: Select all

We're sorry, but Moondust Editor has crashed. 
Reason: Signal Segmentation Violation [SIGSEGV]


================================================
            Additional information:
================================================
Platformer Game Engine - Editor version: 0.3.2.2-beta
Architecture: x86_64 (64-bit)
GIT Revision code: 68a78df
GIT branch: stable
Build date: Nov 22 2022 12:47:05
================================================
Qt 5.14.2
SDL2 2.23.1
SDL Mixer X 2.6.0
================================================
 Please send this log file to the developers by one of ways:
 - Via contact form:          https://wohlsoft.ru/contacts/
 - Official forums:           https://wohlsoft.ru/forum/
 - Make issue at GitHub repo: https://github.com/WohlSoft/PGE-Project

================================================


0   Moondust Editor                     0x0000000102f231a4 _ZN12CrashHandler13getStacktraceEv + 68
1   Moondust Editor                     0x0000000102f24443 _ZN12CrashHandler23doCrashScreenAndCleanupE7QString + 131
2   Moondust Editor                     0x0000000102f2492e _ZN12CrashHandler13crashBySIGNALEi + 558
3   libsystem_platform.dylib            0x00007ff81ddcbc1d _sigtramp + 29
4   ???                                 0x0000000000000001 0x0 + 1
5   Moondust Editor                     0x0000000104366c2d _ZL16indexesFromRangeI5QListI11QModelIndexEEvRK19QItemSelectionRangeRT_ + 445
6   ???                                 0x0000000000000003 0x0 + 3

What are you did to cause this crash? Could you explain your actions to reproduce this crash? Looking at the stack, this was happen at one of dockwidgets or dialogues that contains items on the scrollable area.

Also, please try to download the more fresh Laboratory version of the devkit and try again.

[Wohlstand]

Hello!

There is an important notice about the support of my projects on the SMBX Forum:

I decited to leave the SMBX forums and I will no longer give any support for my projects here on the SMBX forums. All the support is given at official GitHub repositories or at the WohlSoft Forums (https://wohlsoft.ru/forum/), or at the official Discord Server of the team: https://wohlsoft.ru/chat/.

Giving apologies for any inconveniences.

I wish you all good luck. Farewell!