Game Core Crashes When I Run

[Delerna]

I can't run most of the tutorials or my own projects either.
All I get is an "access violation error" and then game core creashes.

I can run the pathfinding tutorial though so I think I am missing something.



OK, here comes a dumb question.
If I do these exact steps
1) create a new "empty" project and save the world
2) Add a "box without collision" and save the world
3) Select Game/Run game
4) Watch the splash screen
5) Select play game on the menu
6) Say OK to the "access violation error" message
7) Watch Game core crash and burn and respond to windows checking for solutions messages

I have logged a request in support but I may get an answer quicker here.
What am I doing wrong? Can someone help me ?

[Javier]

Hi Delerna.

For you own project take a look at this post http://www2.gamecore.ca/forums/index.php?topic=19.msg67#msg67
In that post I expain what is the problem and how to solve it.


You can only "run game" the pathfinding tutorials. The other tutorials are Game Editor only.
Look at this reported Issue http://www2.gamecore.ca/projects/non-game-tutorials-crashes-when-run-game/issuetracking
In the answere Gekido comment this.

[IndieWerks]

I have a lot of crashes too. Randomically. I am not a newbie in programming. Seems a very unprontected code against user errors, by the GameCore looks nice.

[Delerna]

Yee har
Thanks for your help. It all becomes obvious once you see it.
I figured as much with the tutorials (not meant to be run) but I couldn't find the
error of my ways, in my own project.

[Javier]

I have a lot of crashes too. Randomically. I am not a newbie in programming. Seems a very unprontected code against user errors, by the GameCore looks nice.

If you talk about this http://www2.gamecore.ca/projects/a-lot-crashes/issuetracking
try to make an instructions explanation style: First I open the example called XXXX, Secondly I click the button XXXX and check the option YYYY, etc, and now crash. This will help the Gekido's team to find what's the problem and fix it.

[IndieWerks]

Javier, As I said: IT CRASHES Randomically. I know that it is very diffcult to track, but there?s nothing a sequence to follow. Sorry. I will not post about it again. I will use GameCore as a toy.

[IndieWerks]

Just Happend:

1) Create New Project.

2)  create New World

3) Save New World

4) click on main.gls to edit it

POWWWWWWWWWWWWWWWWW!

[Javier]

This is very strange. I hope I can help you but I don't know. I'm only a user like you.
This kind of random errors are very annoying.

Try to unninstall GameCore, delete the entire directory and install again.

Hope you can solve the problem and be happy whit GameCore. 

[IndieWerks]

Yes, I have my assets ready to go, but for my current game, i?m using Blitz3D. It?s for the casual market and i want to release it in 3 months from now. Maybe for the next project, i use GameCore.

[IndieWerks]

Everytime I try do Edit something in Editor, when I save, POWWWW.


Other issue:
I think Gekido could resolve this CRASH when the world is not correctly referenced in Play button with easy.

[Delerna]

Indie werks
I agree, I am an experienced developer (inexperienced with gamecore) and I can't see why an error such as that should be allowed to crash the engine.
It is beta release, I suppose.

Became frustrated with the scripting documentation for GameCore so went to the documentation for BV and followed scripting topics there.
That has been a big help, I understand the file structure for a project and how they relate to each other much better now.
Hope the new guy at gekido can start putting more comprehensive detail into the documents soon.

[Javier]

I think Gekido could resolve this CRASH when the world is not correctly referenced in Play button with easy.

Gekido knows about this problem and probably will be fixed for the next release. 

[IndieWerks]

Yes, Delerna. The docs are very short. I like GameCore. I think they have a lot of potencial. But, the information is spread around many places. I think i have to learn more 6 months to make something playable. One of the best AD of an engine is the games already made with it. I?m trying to put a game with it on market, but since BV 1.0, i have a lot of problems. But I think they will resolve them. Since I decide for Blitz, I can wait more for GameCore.

[gekido]

when you run your game in gamecore, the engine is assuming that some things are setup properly - things like a player (ie an object with a controller script set to handle the camera / input etc).  You can't simply create a terrain, run it and expect to have a game ready to go.  Is this well explained in the current documentation?  No. 

Is this something that we are going to be addressing as we move closer to a final release?  Absolutely.

The release as it stands currently is a 'beta' - ie it is very much an 'in-progress test release' of the engine and tools.  By using the Beta you need to be more willing to experiment and potentially experience strange issues than would normally arise with a finished application.  This is true of any Beta software, and one as complicated as GameCore is no different.

As a result there are things that aren't as streamlined or polished as we want them to be, but we're working on them and making progress every day.

[Delerna]

Hi to the guys at gekido.
Don't get me wrong, I think you have a great product here and I am quickly becomming an avid user.
I totally understand that the software is beta and that the documentation was very light on information because you are
in the process of setting up the site. Having that understanding though dosn't make it any less frustrating.

I say, "the documentation was very light" because I have noticed a lot of new content in the help files. The new guy is going great.
I can see that everything will come together sooner rather than later.

I also said "I can't see why an error such as that should be allowed to crash the engine" because, for me, when writing software,
checking that a file actually exists before I load it is such a basic thing to do when bug proofing my software that I do it instinctively.

I am not saying that "this software is rubbish and I want my money back". Far from it, I am glad to have it now so that I can play with it.
I also accept that the error was totally my own, done in ignorace of the rules, yes , but my own none the less.
I just can't see why an error such as that should ever have been allowed to crash the engine.....sorry.