Rather than make a decision for you, we've added a checkbox so you can decide which trade-off you prefer. This makes a trade-off: it guarantees the game works (if slowly), but in some cases games which by chance don't run in to driver problems, get unnecessarily slowed down. (This happens in the driver's native code - it's not the fault of HTML5, Chrome, NW.js or Construct, it's something everyone developing with computer graphics has to deal with.) Browsers provide blacklists to recognise faulty drivers or hardware and fall back to software rendering. Some systems with poor quality graphics drivers can end up crashing or causing severe display glitches in your game. Ignore GPU blacklist lets you control software rendering in NW.js.Window frame, resizable window and kiosk mode are the same as they were in C2, affecting the style of the window.The main reason for this is to speed up exports: the zip can easily be hundreds of megabytes, and compressing it can often take a while. If you turn it off, the final zip skips compression (using store-only mode in the zip). Compress final zip means the final zip that Construct 3 produces, which contains all the exported platforms, is compressed to reduce its size.Turning off this option means the game files are not packaged (they're simply copied to the same folder), which makes startup faster. This slightly obscures your game's data, but has the downside that NW.js has to extract all the files from the package on startup, which can cause long startup times for very large games. Construct 2 always did this, creating a package.nw file. ![]() Package assets compresses all your game's files in to a single file.This helps speed up exports by skipping platforms you don't care about. The Platforms section lets you select which individual platforms you want exported. This means you always export with the latest version without having to do anything! While you can select any specific version of NW.js from the list, if you leave it on the "latest" option, it will switch to a new version when it's released. The new Latest option is also useful for staying automatically up to date. If you choose one which hasn't been downloaded, it downloads the selected platforms for that version when you export. It may seems less important than PC/Mac, but a lot of publishers/partners set it mandatory now.First of all there's a new version selector, allowing you to switch between any version of NW.js. ![]() Oh, Also, like Prominent, i would be very interested in knowing if the lastest NW.js change something on the Linux front : ) I guess it's time for clean up AND for the leap of faith! I'll keep you posted here.ĮDIT one hour later: nope, even with a clean install, NW.js export works very well with no janks with a Greenworks-free project, but only display a blackscreen with a project featuring the Greenworks plug-in. All I get is a black screen at launch on PC, but I guess having 2 Construct and 2 different Greenworks versions doesn't help. I just installed r197 and I'm now trying to export using nw.js 0.12 alpha3 to see if this fix the Mac problem. I only tried the new C2 builds for pleasure (and they were very very good!) No, by safety, I still was on r186.2 + nw10.5. ![]() Aurel - are you using the latest C2 beta? We fixed an issue with Mac NW.js exports since the last stable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |