preview disclaimer , rename preview mode.

Could we have some sort of warning the first time people run in preview mode that lets them know that their exported game will more than likely be nothing like what they see?

I really feel bad for the people who are making little sub-100 event games, then buying C2 only to find out that they can not even export their project to any of the platforms they were promised.

I am up to 12 projects that have been scrapped because the exported version is nothing like my preview version. (11-node-webkit , 1 CocoonJS)

I already knew what I was getting into when I bought C2. I am just worried about young kids thinking that if they pay for C2 they will be able to export the project they made in the free version, to any platform other than the preview mode.

Maybe it should be renamed from Preview mode to "Mock-up" mode? If the final product is not like the "Preview mode" then you are not pre-viewing anything. A preview would show the bugs.

Maybe pre-blind or Pre-Blurry, mode? Maybe "you might see it if you squint" mode?

I am curious as to what problems you may be having. I personally haven't really experienced any real changes from the preview mode in my exported builds. But that's not to say you haven't. Just curious as to what changes/differences you are experiencing

I assume you're talking strictly mobile here. If someone assumes that preview on PC is the same as preview on mobile, then they are very uninformed.

Movements with delta time.

Just about everything I tried with node webkit. Drag and drop means Save, and open load dialog randomly. Mouse cord's are totally different between preview and exported.(even thought you are previewing in node webkit)

I am spending more time making my projects work like they did in preview mode, than actually making my project.

Well, this topic started out as a request for a preview mode warning... now it is going to be "What JoJoe did wrong to make it export improperly" I am afraid.

Well, this topic started out as a request for a preview mode warning... now it is going to be "What JoJoe did wrong to make it export improperly" I am afraid.

jojoe

Can you explain to us what do you mean by:

"Drag and drop means Save, and open load dialog randomly."

and

"Mouse cord's are totally different between preview and exported.(even thought you are previewing in node webkit)"

because the preview in Node Webkit should be equivalent, if it isn't, I think it is a bug in the Engine (since previewing and exported aren't done the same way), and so should be reported as it if it is the case

> Well, this topic started out as a request for a preview mode warning... now it is going to be "What JoJoe did wrong to make it export improperly" I am afraid.

jojoe

Can you explain to us what do you mean by:

"Drag and drop means Save, and open load dialog randomly."

and

"Mouse cord's are totally different between preview and exported.(even thought you are previewing in node webkit)"

because the preview in Node Webkit should be equivalent, if it isn't, I think it is a bug in the Engine (since previewing and exported aren't done the same way), and so should be reported as it if it is the case

I did report it. I was told that they could not re-produce my windows 7 bug in windows 8... topic is dead. Exporter is still broken for windows 7.

Preview mode works magically though...

Reporting bugs is a complete waste of time for me. I was late for work that day because I uploaded a video.

I've had problems with delta time varying significantly across platforms. I don't use it anymore. I'm not sure this purely related to preview vs export.

Hutto,

Yeah, Me too,Thanks for you input. <img src="smileys/smiley1.gif" border="0" align="middle" />

This is to everyone,

I am not talking about what I or any of you did in the past. The fact remains.

* The results may vary depending upon export method.

* WYSIWYG does not even remotely work sometimes.

* Preview mode is not always what it seems.

My biggest concern here is that no one has to feel the hardships I have had to feel in the past.

The hardships I felt involved multiple days and hours being lost.

The reason I am making this post in the first place is because it would be really easy for the application to give a "Heads up" with a small warning box, upon export.

This is not to bash C2, only to promote it.

I was just asking what you were experiencing. Not bashing or trying to assume you did something wrong.

First of all, you should always be using delta time. removing it is a mistake. Of course it will vary across platforms - if it didn't, it wouldn't work at all.

I have not had any difference between node-webkit preview and export (except some minor performance and rendering differences). Perhaps you could create a capx so we could try to reproduce?

Well, this topic started out as a request for a preview mode warning... now it is going to be "What JoJoe did wrong to make it export improperly" I am afraid.

Well, this seems to be the case else more people would be making similar topics.. Personally I've found node webkit to be the most accurate to the preview. Post some .capx's so we can check them out I guess.

> Well, this topic started out as a request for a preview mode warning... now it is going to be "What JoJoe did wrong to make it export improperly" I am afraid.

Well, this seems to be the case else more people would be making similar topics.. Personally I've found node webkit to be the most accurate to the preview. Post some .capx's so we can check them out I guess.

It is very nice everyone is trying to help me out here. I will post my problems in the appropriate place.(again)

I have a feeling they will be ignored again though. I am not an ally of Microsoft. (I was thought! Night mission rocked my commodore 64!)

My intentions are fully on the promotion of SteamOS and Linux.

This is totally off topic thought... All I was asking for was a little warning for known bugs and limitations.

Must it really be a secret? Must the paying user really have a rude awakening like this?

Why not a warning? Why not a little insight from those who have gone before us and found treachery and sorrow?

Please make bug reports for any issues you see. We cannot correct any bugs if you don't do that.

Node-webkit is based on the Chromium engine, and in the majority of cases runs identically to how it does in Chrome. There should not be any serious differences there.

CocoonJS limitations are documented here: http://www.scirra.com/tutorials/303/how-to-export-to-cocoonjs

Please make bug reports for any issues you see. We cannot correct any bugs if you don't do that.

Node-webkit is based on the Chromium engine, and in the majority of cases runs identically to how it does in Chrome. There should not be any serious differences there.

CocoonJS limitations are documented here: http://www.scirra.com/tutorials/303/how-to-export-to-cocoonjs