Did you manage to get it to work with "Capture Game"? because capture screen and window are working, but they not as optimal for game recording.

I use NWjs 0.18.7 and c2 r239.

Are you sure you are using the current OBS and not OBS classic? Wasn't that "game capture mode" a purely OBS classic thing?

The experimental one never worked for me (not fully anyway).

Prominent

I must say I never had a problem using Madspy's Steam plugin.

—

Yes, this means that "--in-process-gpu" is off the table and not needed anymore?

Btw: thanks for taking the heroic effort and putting up with all the bug reports. We were really in a tight spot with these NW.js shenanigans and now we seem to approach a point where stuff is actually usable for mass deployment again.

So the single process thing was resolved, too?

Sometime 2017 / 2018 or?

So far, no hints have been released to the public.

You have it now. It sometimes takes a bit to appear.

Not trying to dismiss the NW.js problems and their severity, but a certain group of youtubers, reviewers and let's-players are braindead morons (please excuse the profanity). We had *a lot* of issues with them at work, with products made in Unity, Godot and VizRT. Some require spoonfeeding in a way that you get why they make videos for a living and not a decent job

While there is always the need to optimization and there are always caveats, Construct2 takes care of a few things for you that unity does not, by default. For example: C2 does a basic form of object pooling for you. Making a shooter with 2500 objects on screen (with a lot of them being deleted and created) is no problem on a midrange i5 rig. It starts getting a problem if it goes beyond that, but within the limits of a typical arcade shooter you can create and destroy objects like there's no tomorrow. Spray those bullets!

Basically all competitors are releasing new major versions soon.

Spark tools is coming soonish

Spark site

Well, so far they have produced a nice amount of.. vapor.

To be safe: Stay below 2048x2048. (that means: 2046x2046 because of the filter padding added by C2 on export). Older and medium devices (Iphone 4 for example) max out at 2048.

We ought to have this thread stickied (at least until the worst 0.18.x f**kups are fixed)