TheRealDannyyy's Forum Posts

  • Ashley, not really, everything is on default I got firefox installed since 2010 and just recently I noticed that it doesn't seem to find it.

    Although I think that FF 64bit might have changed something but I highly doubt that since I installed it in a seperate folder.

    I know that a user had the same issue with Opera that got fixed in r220, maybe the fix you did there might work with this too.

    How does the previewing work, does C2 check for the default installation path or does it "find" the FF folder by itself?

    (I will reinstall Firefox just to make sure, I mean it's been quiet a while now.)

  • Oh nice, I thought Ashley is only posting news into the C2 forums.

    Thanks zenox98!

    when i open the game, these two processes run

    *UPDATE*

    Using the browser close option DOES seem to close everything. It's when you press the X button to close the window that it stays running

    This seems to be an issue by NW.js and not Construct 2 but anyway Ashley should take a quick look at this just to make sure.

  • Problem Description

    I Cannot preview in Firefox when FF is set as the preview browser.

    (Note that my default browser is set to Firefox and using "default browser" as an option works just fine.)

    Attach a Capx

    Not required since this is from the engine and not any game but here is a screenshot that should help:

    Description of Capx

    It's a screenshot obviously.

    Steps to Reproduce Bug

    • Open any C2 project and have the latest version of Firefox installed
    • Set the preview browser to Firefox
    • C2 returns an error that the browser is not available even if it clearly is

    Observed Result

    Preview with Firefox set as preview option.

    Expected Result

    I expect it to work like the default browser setup works.

    Affected Browsers

    • Firefox: (YES)

    Operating System and Service Pack

    Windows 7 with latest updates and up to date drivers.

    Construct 2 Version ID

    Newest beta release r220 Steam release. [Personal Edition]

    Additional maybe usefull information:

    • Firefox version: 43.0.4
    • Checked C2 data with the Steam software data check system (0 Errors Found)

    Step 2

    Try closing the app

    Does that happen when closing it with the browser event "close" and/or using the default "X" to close a window?

  • You will still remain connected to the Host/Client after changing a layout.

    • Topic Closed -

  • The files in the original report are definitely MP3 files, which is almost certainly the cause of the reported issue. If you think there are any other issues here, please file separate reports for them.

    I wish I could post a report about that but making a bugreport without any way to reproduce the bug would be useless.

  • Ashley It still doesn't explain the issues I had. For some reason I found a solution by creating a .capx instead of a project folder.

    (For me this "fix" doesn't make any sense because there should be no difference between those two saving methods.)

  • Disabling backups has not fixed the issue.

    As you can see we did really try out almost everything that is possible.

    Since we have no sort of source code from C2 to look through (of course private and only accessible for Ashley for copyrights etc.)

    or any hint towards reproducing the bug, I can only say that we simply have to deal with it until C3 comes out.

    (I know that this is will sound a bit mean, but I'm currently dealing with autosaving issues, unexpected audio playback issues and of course this C2 sluggishness so I'd understand if you get kinda frustrated about this. Since there is no clear way to reproduce any of these bugs, hoping for C3 is the only thing what's left for me at least...)

  • Do you have the latest version of C2 and NW.js installed?

  • I seem to be having the same or a very similar issue to that described in this thread. After between 30 minutes and 5 hours of having Construct2 (steam) open, the interface will become extremely sluggish. A simple text entry will take 30 seconds to be processed.

    Alt-tabbing out and back in will result in the current interface 'operation' finishing, but the extreme sluggishness persists. Task manager shows no sign of excessive resource usage.

    This has persisted across multiple machines and projects for at least the last year. The only way to solve it is to close and reopen steam and Construct2.

    I have tried disabling auto-save as suggested by some in this thread, but that hasn't helped.

    If you have backups enabled, could you please dissable them and test if that helps you out?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • — Usually seperating the debug tab from the game preview window results in better performance.

    (But you have to manually seperate it every time you want to debug it...)

  • TheRealDannyyy - does it work after export? In the past we've had a couple of weird preview-only quirks due to the preview server...

    Well Ashley, I tested it a few times with exporting. 15 out of 15 exports were fine so I guess it is not NW.js?

    However I could've been lucky too and it might break on the 16th time, as I said before if you didn't do any changes to the audio or preview systems recently it has to be NW.js and might be fixed in the later versions.

    I'll post a bug report if the later more stable versions of NW.js still have this issue.

  • I can reproduce, but it's very strange: it seems the audio buffer fails to decode only in NW.js, whereas it succeeds in Chrome. I've no idea why that could be. Have you tried r218 and NW.js alpha-7?

    I have tried it and it gets even stranger on my end ASHLEY.

    Whenever it happens I close the preview window, save my project manually then start up the preview again and it works just fine.

    I guess this issue is on NW.js side though and not C2, if you didn't make any changes to the audio plugin recently.

  • Could you please describe the step "Upload as build to gamejolt" a bit more detailed, so I can be sure that it is not an issue by your side of things.