Ashley So we're did some tests, and we see that the freezing only appears on exported project, but in preview mode NWK works fine. Any thoughts?

Also can anyone with Win32 can confirm they are experiencing same issue? It might be win64 only thing.

Yes, loading and saving with node-webkit.

I'm testing the prototype on some different PCs but the result is the same:

My game has one savegame (keeping the player status, the hiscore and the game stats) that loads on startup. When I export the project with node-webkit the game doesn't start (it freezes on the load page). If I export the game without the save/load actions, it works properly.

Any solution?

Don't know. Sorry :/

Normaly I don't use minified with exporting but also tested that out. Doesnt make any difference.

The node-preview is still running and no freeze yet. Did you also use node-preview?

Also trying something else at the moment on another machine. I copied the contents of the node-webkit folder in construct and copied the .pak file from a earlier export that froze and placed it in that folder. It works when I run it and see if that makes any difference. I don't have any knowledge how this stuff works so just messing around now since I don't know what else to do

on preview was fine, but after export it did freeze.

> scaffa

>

> Do you get the freeze with node- preview or just the exported version ?

>

I was unaware you could do a node-preview, thanks for mentioning that. I have been running the node- preview for an hour now with my actual game project and had zero freezes so far. Will keep it running for a bit longer.

One step closer to the problem.. So maybe it's a problem that occurs during the export proces with the windows version?

Since my experience so far is that the mac version works without problems. And now the node- preview works without problems. Maybe a silly question but is it possible to retrieve that node-preview version somehow? Is it located someone temporary?

megatronx Again thanks for your help and good to hear you are not experiencing the problem.

Np. But I was running it in preview. I'll try exe now.

EDIT@ Yes you can. Can't remember where it is located exactly but it is somewhere in you document files folder.

EDIT2@ Not sure if that's possible with NWK but are you exporting script as minified ?

EDIT3@ NVM, after exporting it did freeze after 20 mins!

SHITE!

Hi everybody

any chance to export a game with savegames using the node-webkit tool?

thank you in advance

What do you mean? I thought you can savegame in NK?

Running it for almost 2h now and no problem yet.

>

> >

> > I remember I had that issue a year ago. I can't recollect if I found out what was cause those freezes back then or not. But on current project nothing happened like that yet ( and I want it to stay that way ). If you could share your jumping boxes capx, or better exe with us, we will tru it out too.

> >

>

> I spoke with someone else and he also mentioned he didnt have any problems with the node-webkit export. So maybe something goes wrong during the export? I have no clue.

>

> I uploaded the files to MEGA but I cant post a link here so I will send a pm if that is possible. Attacked the capx for the jumping box project right here. Testing this problem is kinda yeah not fun since it can take a while to happen if you are 'unlucky'.

>

> edit: Seems I cant send pm's at the moment and add links due to low reputation.

>

> [attachment=0:aoujq8hc][/attachment:aoujq8hc]

>

There's the attachment Running it now

Edit@ Clean so far. Hmm, trying to remember what did I do to get rid of those freezes long time ago. Might have been one of the following: gpu drivers, dXdrivers, .net framework, or something was running in the background ( music or graphic software )

>

> I remember I had that issue a year ago. I can't recollect if I found out what was cause those freezes back then or not. But on current project nothing happened like that yet ( and I want it to stay that way ). If you could share your jumping boxes capx, or better exe with us, we will tru it out too.

>

I spoke with someone else and he also mentioned he didnt have any problems with the node-webkit export. So maybe something goes wrong during the export? I have no clue.

I uploaded the files to MEGA but I cant post a link here so I will send a pm if that is possible. Attacked the capx for the jumping box project right here. Testing this problem is kinda yeah not fun since it can take a while to happen if you are 'unlucky'.

edit: Seems I cant send pm's at the moment and add links due to low reputation.

[attachment=0:morfmucp][/attachment:morfmucp]

There's the attachment Running it now

I will do another test with less programs running. But I have been testing this morning with my current pc and also with a surface tablet that doesnt run alot of programs at the moment. Both have this problem.

Friday with another test on someone elses machine that had a clean windows install also showed this exact problem.

If it's happing on each windows (7 and 8) machine that I play the game on then that doesnt bode well.

I remember I had that issue a year ago. I can't recollect if I found out what was cause those freezes back then or not. But on current project nothing happened like that yet ( and I want it to stay that way ). If you could share your jumping boxes capx, or better exe with us, we will tru it out too.

Ashley Did some further testing and hope you can respond to this problem, if there are plans to fix this and what can I do to fix this?

Did some further testing and it didnt matter what I changed it still happened. So I made a new clean project and didnt change any settings.

The project has two sprites and only one event. Once the sprite with a player behaviour makes collision with the floor sprite it jumps and plays a sound. As simple as that.

You can see the result here: youtu.be/i635UHoviMk

At 1:19 it freezes up till 1:46. Then it continues playing again. This is a huge problem with the node-webkit exporter and if there is no alternative way to make an proper executable for windows then heck what can I do now?

I'm thinking, do you have any programs running in the background? If so, could you do a test with all closed?

I'm not a programmer but I'd imagine that Ashley would have to write a completely new loader, that would request assets sequentially and not too fast - one by one, or part by part, but with some breaks, and somehow be integrated in to the event sheet loop ( and I don't mean events, but just making sure the game will run while and loadding assets wont take much away from games fps). It would be definitely very good to have.

I can understand why you might be reluctant to incorporate this at the risk of confusing less experienced users, but that's why it could be an advanced option so the more experienced users can use it instead. Professional games use loading screens in this manner quite often, it would be very useful for us to be able to do the same if we want to. While C2's memory management as it is is fine for many games, it isn't optimal for all types of games, and this way we could choose how we want it to

The confusion could be solved by having a button that would toggle on/off advanced actions from the view. But I guess no point having that just for one action.

It's not a VRAM issue. Pauses still happening for projects with only 1 or 1000 objects. They happened on my old geforce 570, then on my Intel integrated graphic card and now it's pauses on new geforce 780 with 3 GB of VRAM. But not always, it's very random, In some projects with few hundreds of events and objects I've never had any pauses. And on some projects with only few events/objects it's pausing every time after few seconds in the game.

So basically it's shit sandwich. All we can be certain is that things will work in FF and Chrome. That's charming. What I've got from that steam thread is that even if the game works perfectly for you, others will have issues.