I just want to pretend all rumors that the development of GameEdit stopped. ATM GameEdit can be tested in the beta-forum and I'm really getting closer to the finish.

Sorry for the extrem delay. It was much more complicated as I thought.

god, that looks sooo beautiful, and you said in the beginning that it wont be hard to incorperate into our script? thats wonderful.

I suggest a text menu in the upper row, just like every windows application in addition to your iconized menu. I really feel uncomfortable working with it (current beta).

Your forgot to translate "Skalieren"

@lostclimate I mean hard is relativ. Things you have to do:

1) Include Game Edit:
Code:

---

path "C:\\Programme\\Beta\\Map-Editor\\Scripts";
path "C:\\Programme\\Beta\\Map-Editor\\Hud Data";
path "C:\\Programme\\Beta\\Map-Editor\\Modelle";
resource "C:\\Programme\\Beta\\Map-Editor\\Scripts\\GEdit_Scripts.wrs";
include <material_editor.wdl>;

---

2) Init GameEdit in your main function
Code:

---

material_init();

---

Thats all

@Firo: fixed, thanks for the hint

How about writing a script doing all that stuff for you?
So you only need to include the gamedit.wdl which contains the path statements and a starter function.
Would be even easier - or are there any problems with this?

Just an idea...

Of course material_init(); Could be also a starter function.

Than only the Paths, The Resource Statement and the Include Statement lasts.
The user have to write the paths, because of course every User installs 3D-Gamestudio in other directorys.

Actually all code you see is only in order to get the include statement working..

The most complicated thing was the Save/Load system of GameEdit (Actually sometimes it may be still a problem). Why? Pretty easy. I don't have ANY influence into the WMP and $$M format. That means I have to write and parse the WMP / $$M 100% correctly. If I would wrote an own file format I could have often used easier ways (no object groups like in the WMP format, less information - paths! - etc.).

A second big problem is simply said C-Script. In C++ you could parse a big WMP (3MB +) file at once (because of local strings, delete/new instructions etc.). I have to split the WMP file into 50KB chunks. This will result into new problems (The WMP file itself consits of Object Cunks). If I split a file into 50kb chunks I can not say if after 50KB there is a block I would have to read.

A I forgot.. The 3rd problem is that I often have to think around 4 corners. Why? Because I'm not allowed to change ANYTHING of the User-Objects / Map etc. if he don't want me to do this. I'm not allowed to Save temporary data into skills, because they might be filled. I'm not allowed to temporary change some Material information, because they might be filled with some other information.

There are many many other problems.. but okay