Moondust Project thread [Support moved]

The0x539 · Postby **The0x539** » Fri Jun 09, 2017 8:00 pm

TheGamingCats wrote: The PGE tester has so many bugs though.

Use LunaTester, the PGE/Moondust Engine isn't ready for primetime, and it was a mistake to imply otherwise in Beta 3. I recommend you update PGE, but you can also just use the LunaTester button or press F5.

TheGamingCats · Postby **TheGamingCats** » Fri Jun 09, 2017 8:25 pm

The0x539 wrote:
TheGamingCats wrote: The PGE tester has so many bugs though.
Use LunaTester, the PGE/Moondust Engine isn't ready for primetime, and it was a mistake to imply otherwise in Beta 3. I recommend you update PGE, but you can also just use the LunaTester button or press F5.

Yes I know. I use LunaTester. I'm just saying that the other tester is bugged

The0x539 · Postby **The0x539** » Fri Jun 09, 2017 8:48 pm

The tester's not bugged, it works just fine. The engine isn't bugged so much as incomplete.

TheGamingCats · Postby **TheGamingCats** » Fri Jun 09, 2017 9:24 pm

The0x539 wrote:The tester's not bugged, it works just fine. The engine isn't bugged so much as incomplete.

Oh, I see. Why are there 2 testers in the first place anyway?

The0x539 · Postby **The0x539** » Fri Jun 09, 2017 11:13 pm

TheGamingCats wrote:
The0x539 wrote:The tester's not bugged, it works just fine. The engine isn't bugged so much as incomplete.
Oh, I see. Why are there 2 testers in the first place anyway?

Because there are two engines, and Moondust Engine devs need to be able to test the engine.

TheGamingCats · Postby **TheGamingCats** » Fri Jun 09, 2017 11:30 pm

The0x539 wrote:
TheGamingCats wrote:
The0x539 wrote:The tester's not bugged, it works just fine. The engine isn't bugged so much as incomplete.
Oh, I see. Why are there 2 testers in the first place anyway?
Because there are two engines, and Moondust Engine devs need to be able to test the engine.

I see..

Wohlstand · Postby **Wohlstand** » Tue Jun 13, 2017 6:44 pm

Hello, everybody!

Important news, please read!

Recently we found a massive bug in Version 3.0 (older versions aren't affected) of the GIFs2PNG tool: When trying to convert images using a config pack and having the "-r" flag (remove source images) set, GIFs2PNG would also remove masks from the config pack!

We have updated the PGE Project builds to update GIFs2PNG to Version 3.0.1 which fixes this bug!

The next update to the PGE Project will come soon after we complete a lot of work on the engine application. The editor is preparing for a big reorganizing and will have many new features!

See you soon!

Yoshi678 · Postby **Yoshi678** » Thu Jul 27, 2017 9:39 am

I need help pretty urgently. I ran the "fix bad masks" tool and this happened. How can I fix this? (I'm so sorry if this is the wrong thread for this but like I said, it's pretty urgent.)

Wohlstand · Postby **Wohlstand** » Thu Jul 27, 2017 9:43 am

Yoshi678 wrote:I need help pretty urgently. I ran the "fix bad masks" tool and this happened. How can I fix this? (I'm so sorry if this is the wrong thread for this but like I said, it's pretty urgent.)

Did you keep source pictures? I would analyze them because I think, your combination front+back just produces this. Especially on the non-black background of the front picture. If the front picture was invalid too (I mean, non-black background), a result will be glitchy even after lazyfixtool.

Yoshi678 · Postby **Yoshi678** » Thu Jul 27, 2017 11:49 am

Wohlstand wrote: Did you keep source pictures? I would analyze them because I think, your combination front+back just produces this. Especially on the non-black background of the front picture. If the front picture was invalid too (I mean, non-black background), a result will be glitchy even after lazyfixtool.

Um.. Sorry. I'm rather new to PGE (It's a good program by the way.) and I'm not too sure of the technicalities of it. Could you clarify what you mean by "source pictures" and what you're asking me to do? Thank you.

Wohlstand · Postby **Wohlstand** » Thu Jul 27, 2017 11:55 am

Yoshi678 wrote:
Wohlstand wrote: Did you keep source pictures? I would analyze them because I think, your combination front+back just produces this. Especially on the non-black background of the front picture. If the front picture was invalid too (I mean, non-black background), a result will be glitchy even after lazyfixtool.
Um.. Sorry. I'm rather new to PGE (It's a good program by the way.) and I'm not too sure of the technicalities of it. Could you clarify what you mean by "source pictures" and what you're asking me to do? Thank you.

"Source pictures" I meant original pictures are was before you ran mask fixer (LazyFoxTool's backend)

Yoshi678 · Postby **Yoshi678** » Thu Jul 27, 2017 12:57 pm

Wohlstand wrote: "Source pictures" I meant original pictures are was before you ran mask fixer (LazyFoxTool's backend)

I hope this is what you're after:

Before Fix Tool:

After Fix Tool:

RudeGuy · Postby **RudeGuy** » Fri Jul 28, 2017 3:45 pm

he meant the original graphics.

Yoshi678 · Postby **Yoshi678** » Mon Jul 31, 2017 12:57 pm

RudeGuy07 wrote:he meant the original graphics.

The original graphics hm? You mean the graphics as they were before I dragged and dropped them into the level folder? I have a folder with all my downloaded graphics in it so I'm gonna say yes, I do have the original graphics. If what you're suggesting is that I just take the original graphics and replace the ones in my level folder, I've tried that and it didn't work.

RudeGuy · Postby **RudeGuy** » Mon Jul 31, 2017 1:43 pm

yes, those. why don't you try giving them to us? we can fix them.

Wohlstand · Postby **Wohlstand** » Tue Aug 29, 2017 5:18 pm

Greetings hoomans!

Here's a quick rundown of some (hopefully exciting!) news from the PGE devs for y'all.

We're releasing new versions of the Engine, Editor and other tools. These include small feature additions and numerous bugfixes for known bugs and crashes. This update also adds improved support for 38A level files and read-only support for 38A-formatted world maps.
PGE also finally has 64-bit assembly support for Windows (previously 64-bit support only went as far as Linux and macOS).

We're rebranding! The project you've known till now as the PGE Project will now be rebranding itself as the "Moondust" Project. For anyone feelin' out of the loop: For a while now, our devs have had the intention to have a project name that not only felt easier to remember, but something that had a more unique distinctive brand to reflect the project.

We think we've succeeded in figuring that out, and I'd like to thank everyone who participated in voting and/or provided feedback!

We're beginning a rather massive reorganization of the editor.
Yess it's true! The Editor is set to recieve a major overhaul and will be completely rewritten. Don't ring those alarm bells yet though! The existing editor will still be supported fully till we can get its replacement complete and up and running.

Article credits to Nexiana

All downloads have been updated

Editor changelog 0.3.1.12

Spoiler: show

Engine changelog 0.3-alpha

Spoiler: show

arcade999 · Postby **arcade999** » Tue Aug 29, 2017 5:27 pm

Hmmm, but how do I replace the old PGE editor my version of smbx 2.0?

Wohlstand · Postby **Wohlstand** » Tue Aug 29, 2017 5:37 pm

arcade999 wrote:Hmmm, but how do I replace the old PGE editor my version of smbx 2.0?

SMBX2 uses laboratory version, and to update it safe, you need use a special script which will download latest PGE package and will replace all binaries:
Read this manual "how to update PGE in SMBX2 Beta 3+": http://wohlsoft.ru/forum/viewtopic.php?f=11&t=1977