I try to set the material of a heightmap field in the Custom Editor mode...

Now I'm getting errors that are really confusing to me:


I get the following errors:

1>c:\users\gian-reto\documents\local\esenthelenginesdk_new\editor\texturizer.cpp(175): error C2558: struct 'EE::Image': Kein Kopierkonstruktor verfügbar oder der Kopierkonstruktor is als 'explicit' deklariert
1> Diese Diagnose trat in der vom Compiler generierten Funktion "EE::Edit::Heightmap::Heightmap(EE::Edit::Heightmap &)" auf.
1>c:\users\gian-reto\documents\local\esenthelenginesdk_new\editor\texturizer.cpp(175): error C2558: struct 'EE::Image': Kein Kopierkonstruktor verfügbar oder der Kopierkonstruktor is als 'explicit' deklariert
1> Diese Diagnose trat in der vom Compiler generierten Funktion "EE::Edit::Heightmap::Heightmap(EE::Edit::Heightmap &)" auf.
1>c:\users\gian-reto\documents\local\esenthelenginesdk_new\editor\texturizer.cpp(175): error C2558: struct 'EE::Image': Kein Kopierkonstruktor verfügbar oder der Kopierkonstruktor is als 'explicit' deklariert
1> Diese Diagnose trat in der vom Compiler generierten Funktion "EE::Edit::Heightmap::Heightmap(EE::Edit::Heightmap &)" auf.
1>c:\users\gian-reto\documents\local\esenthelenginesdk_new\editor\texturizer.cpp(175): error C2558: struct 'EE::Image': Kein Kopierkonstruktor verfügbar oder der Kopierkonstruktor is als 'explicit' deklariert
1> Diese Diagnose trat in der vom Compiler generierten Funktion "EE::Edit::Heightmap::Heightmap(EE::Edit::Heightmap &)" auf.

translated to english:
1>c:\users\gian-reto\documents\local\esenthelenginesdk_new\editor\texturizer.cpp(175): error C2558: struct 'EE::Image': No copy constructor available or the copy constructor is marked as 'explicit'
1> This diagnosys happened in the function generated by the compiler "EE::Edit::Heightmap::Heightmap(EE::Edit::Heightmap &)"


Now I didn't change the EE::Image class, and the code above contains the only call to Edit::Heightmap in the whole class... any idea what could be the problem here?

Okay, I think I have now an idea what could be wrong. I think I just have no idea how to use the MaterialPtr class.

This is how I initalize my material pointers:


Any chance someone could give me an example how to do that better (as in, the correct way)?
It seems to me, now that I think of it, that I might want to get the materials from the material palette. Loading them directly from a file would be better though, if that is possible....

.gfx is not materials they are images, you have to either make materials with those images or

MaterialPtr ptr;
ptr->base_0.get("Just Add Bison.gfx", mtrlPath);

Thanks for the reply, Zervox

Sadly I tried your suggestions, but the error is still the same.

In the header file for the Heightmap.setMaterial Method, it seems that the function is expecting MaterialPointers. How could I make the materials, so that the function doesn't need to do it (As it seems to me it does something wrong while creating the images)? What do I need to do?

My suggestion was a MaterialPtr which shouldn't be a problem.

Yes, thats what I use. But it seems there is still some EE:Image involved, and some method tries to invoke the copy constructor...

Quote:Edit::Area(VecI2(iteratorTX,iteratorTY), user);
Edit::Heightmap(*a.heightmap()).

just a note: you're trying to create new temporary variables which is incorrect, you should access those already available from World.

Hi Esenthel

How do I access those? I don't see where in the code this is done...

I'm sorry but I think I need a little bit more help with this problem, I can't figure it out by myself.

EDIT: Okay, first part of the mystery solved.... still, even with the "World Editor.h" file included I don't see how I access the ares of the exisiting world

In "Edit Area.cpp" for example there is a call to area() from "WE Area.h" without any object present. I don't see any code that makes Edit Area extend from WE Area (though that could be me beeing a C++ noob)...
How on earth does that work? Is this the Method I should call to get the actual areas from?

Hi, I wrote to you in a different thread that World Editor source code already has a tutorial for editing areas. you access them by World.grid.

Okay, I'll try it with World.grid.... I found the call to it in the editor code, even though its a single line, commented out. But maybe I'll be able to figure it out.

I changed the way I get to the Area / Heightmap, but I still get the same errors as noted in the opening post.

The code involved (minus a lot of logic that has nothing to do with the materials itself) looks like this at the moment:


Whats the problem with the materials?
Why does setMaterial try to copy the materialPointers?

Please don't keep emailing me asking for help - http://www.esenthel.com/community/showth...p?tid=3331

according to the EE headers you need to call:
1. once Edit::Area::setChanged before making any change
2. call hm->setMaterial on each pixel
3. once Edit::Area::hmChanged

also your codes have many mistakes:
((Edit::Area*) Edit::World.grid.get - you shouldnt do any manual casting

MaterialPtr rubble;
rubble->base_0.get("Fractured Flow.gfx", mtrlPath);
you cannot load material from a texture:
MaterialPtr rubble="path to material/mtrlfile.mtrl";

you should look at the cpp tutorials in the SDK folder to learn the basics about handling EE functions.

Ok, thanks for the help... I'll correct my code and see if I get it to work now.

EDIT: Got it to work, but I get an Unknown Exception when calling my texturizer Function. Well, anway, one step further, still not there...

EDIT 2:

I get an access violation when calling


area is now defined this way:


I'll try to narrow the problem further down, but after looking at the tutorials I see the method used elsewhere, there it seems to work... so it must have something to do with the way I get the area and/or the heightmap of this area...

maybe the "heightmap()->" is NULL and you need to call hmCreate first?

also please make sure to operate only on areas within the range of World.visibleArea()
other areas are unloaded and applied changes will not be saved, then you can call World.cameraGoTo(area) to move camera, wait a few frames until new areas are loaded, and apply changes to them.

I don't check for null in my code, but I am pretty sure that there SHOULD be a heightmap as I call the method on a loaded world with a heightmap.

The second possibility though makes a lot of sense.... I start at x=0, y=0 and try to iterate through to x=2048, y=2048 (well, not literally, as I call one area after the other (32 in each direction) and then all heightfields on these (64 in each direction), but you get the point), without moving the camera anywhere.

Is there a possibility to just load the heightmap for a certain area into memory, and unload it after all heightfields of an area have been processed, or is moving the camera the easiest way?