Toby R's Forum Posts

  • That paragraph from Streamer 3. mmmhm

    Imagine what "Twitch ready" would do for sales.

    Really? Out of the whole post this one paragraph interested you the most? The important part on this screen is "that does solve my recording issues".

    BTW: He was refering to being on the Twitch apps list (or not). You cannot stream a game which is not on that list so he was just encouraging to add the game to the list.

  • "chromium-args": "--disable-plugins --disable-internal-flash --disable-popup-blocking --enable-gamepad --enable-html5-camera --allow-file-access-from-files --disable-software-rasterizer --ignore-gpu-blacklist"[/code:273hc5oq]

same than yours

Additionnal note: I don't test on steam game but I guess it works because I found gameplay video of game created with C2 on youtube or community hub (nw.j 14/17/18)

    Alright, thank you for testing.

    Yes it is possible. No one said it is not possible. It is possible if you use OBS and set it up correctly, it is also possible with some other recorders if you launch app and recorder in proper sequence (well that works sometimes, kinda randomly).

    Let me paste part of my conversations with few youtubers who managed to record my game gameplay.

    == Youtuber 1

    He was not able to record the gameplay, still he didn't give up and ended up using a trick and record a video.

    == Youtuber 2

    This youtuber gave negative review on Steam after playing 0.1h (so 6 minutes).

    Part of his review was

    it's in Russian, but when you put it to Google Translator it's understandable. He says that the game is bugged and impossible to record.

    I doubt he played those 6minutes. I believe he was trying to record the game and got simply frustrated so just left a negative review.

    == Youtuber/Streamer 3

    This one contacted me telling he has recording problems. I asked him to try to launch the app first and then the recording software.

    I have more complaints on my emails somewhere. Those were just easy to find. I don't want to spend too much time searching for all of them now, but I think it's clear even with those few examples. After all I had several letsplay videos from few youtubers out of 69 youtubers who were willing to record the game. Those small unknown YT guys will spend some time to find out the way. But any bigger youtuber will obviously not bother at all as he has a long list of games in his queue.

    So after all it is possible to record the gameplay, but not that easy with most of the recording software.

    I hope that clears things out.

  • Ah, yes with OBS it works we know that as OBS gives you possibility to precisely select the source.

    Still could you tell if you use any non default chromium options. By chromium options I mean the chromium-args section in package-win.json file. Do you use any other than those:

    "chromium-args": "--disable-plugins --disable-internal-flash --disable-popup-blocking --enable-gamepad --enable-html5-camera --allow-file-access-from-files --disable-software-rasterizer --ignore-gpu-blacklist"[/code:1zd0ubau]

Thanks

  • Hi,

    Recording fullscreen at 1920x1080egf@48fps https://www.dropbox.com/s/wy6t92e15ynns ... 2.flv?dl=0

    Nw.js 0.18.5.

    Regards,

    Can you provide some more details please?

    * What screen recorder have you used?

    * What chromium options apart of the default ones?

    * Have you launched the screen redorder first or the app?

    Thanks

  • Well, reality check then.

    We're not getting a native export.

    Fraps hasn't been updated since 2013. No idea of what the paid versions get.

    Getting people to update third party software isn't viable anyway.

    Am I all caught up?

    The options are:

    Self recording.

    Exporting to a platform that can be recorded, such as Edge, W10 Uap, Firefox, etc. Did someone say demo?

    Using third party software that can be pointed at the correct instance, such as Obs.

    If you can't work with that then I am sorry, and perhaps you should just give up.

    I must say that encouraging to give up on fixing C2 problem by C2 user is at least weird. Why would we? I love this engine and I want to be able to build fully working PC games. If there are chances I can do it - I'll give it a shot. I personally think that it should be more Ashley's concern than mine, but as he's not really interested in fixing this one, I'll give it a try. I much rather fail than not to try.

    Also there is still a hope that NW.js team can fix it as I mentioned here. Flickering issue is already reported, so we'll see.

    If both flickering and recording issues will not be fixed. Then another solution will be switching from NW.js to Electron. But we will need a bunch of new plugins for that. armaldio is currently working on those: http://armaldio.xyz/electron-plugin and it might turn out to be our future. I already tested the Electron build (provided by Armaldio) of capx from flickering bug report and I had no flickering there, so it looks promising so far.

  • OK, I tried.

    There's no work around, and no point in even trying to use some other method to record let alone make games in Construct 2 any more as your Youtube overlords can't be arsed to try something else.

    I thought I was hard up, using depression as an excuse for a lack of creativity , but geez, not releasing a game because it can't be recorded beats my pickle.

    Unfortunately youtubers are the most powerful marketing "tool" we - indie developers - currently have. I do understand your point of view if you are not releasing any PC game currently. Most of devs on this forum don't care about this issue because it's not their problem (yet). Same goes for the screen flickering issue BTW.

    But for a person who spent months developing a game which is just about to be released to Steam it's a different story. The point is that you can launch the game only once. And this is the time when you get an overall buzz. The time when youtubers contact you via KeyMailer and similar systems. If you won't use this time the right way, your game gets burried and you can't really do much later on - or at least it is much harder.

    I also understand youtubers who simply dump the game which gives any recording problem. They need to have clips published frequently to keep their business and they have a lot of games in queue all the time. Why would they bother trying various tricks if they can simply jump to the next one? Unless it's an anticipated game, they have no reason.

  • — Is the simulator working for you?

    FYI: I have updated AC plugin and linked newest AC library to the controller and simulator worked straight away for me with my old project.

    You can see it here:

    https://puu.sh/sksDF/69c6b4673d.png

    https://puu.sh/skszs/5daa0dda91.jpg

  • How self recording can be useful for a youtuber who just opened your game and want to record a Let's Play video?

  • > I have reported this issue to Action Mirillis (https://mirillis.com/en/) and FRAPS (http://www.fraps.com/) for now. We'll see if they'll take care of it or not. If those two will ignore it, then there's no point in reporting the issue to others I guess. I'll keep you updated.

    >

    >

    Any way I can back you up on those reports? Should I just file a similar issue? This issue affects me enough to the point where I'm going to make my voice heard and be a pain about it.

    I explained them that it is not only my issue but a C2 community issue and that I can encourage the community to make more reports if it's needed. So I don't think more requests are needed for now. But I think those companies don't really care. I mean those recording programs are there for years now and they are selling well, so they might just don't care or simply think that it's a C2 issue. It would be a different case if it was just one screen recorder which can't record C2 games, but the problem is that most of them can't record C2 games.

    Anyway FRAPS did not reply anything yet. Action Mirillis replied that they will try to reproduce the issue. I am a premium user of Action Mirillis so they kinda had to reply something.

    To be honest I am not very optimistic in this case. Even if we manage to "force" few recorders to change something in their screen detection, I highly doubt we can force them all, and after all there are new screen recorders coming out frequently so we would have to keep on asking them to make such "fix" on and on.

    But I hope this issue is related to the screen flickering issue. When I try to record C2 app, then sometimes (randomly):

    • it doesn't detect the app at all like here:
      Subscribe to Construct videos now
    • it kinda detects it while the flickering occurs, but then it turns the screen black like here:
      Subscribe to Construct videos now

    The flickering issue has already been reported to NW.js (https://github.com/nwjs/nw.js/issues/5477). Let's hope they will not ignore it and fixing one issue will fix the second one. By the way I encourage you to upvote this issue on their GitHub, it will probably speed up the fix.

  • We've gathered pretty much details after some investigations regarding this issue which should help fixing the problem. TheRealDannyyy has already created a bug report on NW.js GitHub. Your upvotes will surely help so please take a look on the bug report whenever you have a moment. Thanks.

  • I've only sporadically been able to see the flicker, I can't reproduce it reliably, but I think I've seen it happen.

    So you knew the bug is there. This issue is there already for around 8 months. I believe it wasn't reported earlier because C2 community is very small and not many people update NW.js to the newest version each time it comes out. Also not many people actually make desktop games (mobile dev are majority I guess) and over that, it doesn't happen on every machine. And of course, most people don't care/bother to make a report.

    So because C2 community is small it looks like it doesn't happen that often. But it does happen. And now imagine that someone makes a successful game which gets thousands of downloads on Steam. Customer review section would turn red for sure. So I just wanted to highlight that for whatever reason it is, your product is not able to provide a well working desktop app at the moment with the latest NW.js version (I mean the one which is able do be downloaded from Scirra's site). And until this is fixed by whatever party I suggest to announce NW.js 0.13.2 as recommended version for Construct 2 - just in case someone makes a great game and bring a huge sh*t storm on C2. So that's just my suggestion. Of course you will do whatever you find right.

    It seems to only happen in fullscreen mode in NW.js, not in windowed mode, and not in fullscreen mode in Chrome. Can you confirm this is the case for you too?

    Yes. We already mentioned that few times on the post related to this issue. It only happens in fullscreen mode in NW.js 0.14.x and up.

    If it's specific to NW.js there's not a lot I can do - I'd recommend reporting it directly to NW.js. One tip though: tests are better when they don't need user input, just replace the mouse click event with every 0.05 seconds or something like that.

    I've edited the bug report (first post here) and added automated capx.

    This capx has only two events:

    Another thing I noticed is the dependence between the sound trigger interval and the sound's duration. The sound in the capx is 0.253s long. If we loop it to be triggered with 0.3s or higher interval then the flickering issue occurs.

    However if we set Every X second condition to 0.1s for instance then the flickering does not occur. Also when we simply trigger this sound as looped, the flickering does not occur.

    I don't know what's inside the Audio plugin, but I'm guessing that there's a - let's call it - "silence" trigger after the particular sound stops playing. It must be something common of Audio->stop(tag) function and when the sound has ended.

    So it's not Audio->play(tag) which causing this flickering, but the end/stop of playing the sound.

  • What worked for me was d3dgear.com with NW.js 0.13.2, but you had to run the game first and then the recording soft.

  • The problem is related only to full screened NW.js

  • I have reported this issue to Action Mirillis (https://mirillis.com/en/) and FRAPS (http://www.fraps.com/) for now. We'll see if they'll take care of it or not. If those two will ignore it, then there's no point in reporting the issue to others I guess. I'll keep you updated.

    — AFAIK there's no NW.js version which works well with all screen recorders.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • I asked for help with testing on Construct 2 Facebook group (https://www.facebook.com/groups/constru ... 876321205/).

    One person says he has this issue on Windows 7 Ultimate. So it turns out it's not OS dependent.