Question about deployment and size.

[_Shadow_]

I stripped my project from unneeded assets and tested a creation of a game for Windows.
Main exe becomes nearly 45MB.
Then I notice a file, pdf.dll, being 11MB itself and I am not sure if it is needed at all. I mean I can run the project without any problem.
So, bottomline, here are a few questions I have.

1. Can I exclude this file from my game deployment without any legal issues?
2. What is its purpose?
3. Why is the executable so big? It's like minimum size of a project is around 70MB. Back when we used VX Ace we had to include the RTP but there was the workaround to make a stripped version of that rtp folder, thus make small games, around 25MB or something. Is that the price we have to pay for cross platform compatibility?

EDIT: I would say a nevermind here, because I exported the tiny web version. But I would like to know.

 

[Shaz]

I don't really have answers to your questions - just suggestions.

Re the pdf.dll - remove it and send the game to someone who doesn't have MV installed. If they can play without any issues, the file is probably not required. I have no idea what it's used for. I can't see that there'd be any reason you'd have to include it for legal purposes.

What is the audio format for the platform you're deploying to? Does it result in larger files than the format required by Ace? When you removed unneeded assets, did that include animations you weren't using, and states that you weren't using, or did you leave the animations tab as it was when the project was created and just add new ones? There are a lot of animations and the files for them are pretty large (and they use audio, so not removing them could result in some audio files being included that aren't actually used in your project).

 

[_Shadow_]

Question about deployment and size.
Your 35000th message. Wow @Shaz .

I pretty much stripped the whole set of assets included, the Animations, that were significantly big.
I mean it, almost everything was stripped.
What was the biggest file needed was the exe and I have no idea why.

The web deployment comes out as a 5 to 6 MB file and it is awesome though.

 

[Shaz]

Your 35000th message

lol - and I completely missed it!

With Ace, the exe was small because all the game assets were compiled into the .rgssad file. That one probably would have been pretty large. With MV, maybe the exe contains the assets? And for web deployment, I believe the assets are not bundled and are downloaded as required, but could be wrong on that.

 

[TWings]

MV's exe doesn't really contain any vital assets directly related to RM actually. It's mostly NWJS.
You can actually even update the NWJS version by replacing the files (including the game.exe) with the latest NWJS files.

 

[_Shadow_]

MV's exe doesn't really contain any vital assets directly related to RM actually. It's mostly NWJS.
You can actually even update the NWJS version by replacing the files (including the game.exe) with the latest NWJS files.

In this case, the exe probably creates the container of the NWJS project, meaning the window (or fullscreen) that will run smoothly in Windows. Does it have to be THAT big though?

 

[caethyril]

Not certain, but I'd guess it's because an HTML5 deployment is run through a locally-installed browser, but an OS-specific deployment has to be bundled with something that'll run it (Chromium in this case). Basically it's 45 MB because it's a browser and a game in one package.

I don't know what the pdf.dll is for, though.

 

[Aloe Guvner]

As far as I can tell from browsing some Github issues, pdf.dll allows nw.js to use the window.print() API to print as PDF.
You should be safe to get rid of it from your deployed files (but of course test, just in case )