sapier wrote:@rubenwardy yes it is. It's based uppon Qt so it'll be easy to compile for any os you like.
I'm sorry I've been annoyed about nodebox creation for mobf yesterday early morning and started to write the editor. I didn't know you're working on a nodebox generator that time.
WIM is a quick and dirty solution it doesn't support editing in 3d mode, drag drop boxes, resize boxes in 3d windoe ... .I don't think I'm gonna add it. Like all quick solutions wim's internal design isn't very sophisticated. It does what I require it to do no more, no less.
There are still some checks missing, error handling ain't done the way it helps user to fix what he's done wrong.
function x(value)
return (value - (160/2)) / 160
end
function z(value)
return (value - (160/2)) / 160
end
function y(value)
return (value + (160/2)) / 160
end
local nodebox_test = {
--X1
{ x(-176.000),y(-64.000),z(96.000),
x(336.000),y(-96.000),z(64.000) },
--Y1
{ x(64.000),y(176.000),z(96.000),
x(96.000),y(-336.000),z(64.000) },
--Z1
{ x(64.000),y(-64.000),z(336.000),
x(96.000),y(-96.000),z(-176.000) },
--X2
{ x(-160.000),y(-48.000),z(112.000),
x(320.000),y(-112.000),z(48.000) },
--Y2
{ x(48.000),y(160.000),z(112.000),
x(112.000),y(-320.000),z(48.000) },
--Z2
{ x(48.000),y(-48.000),z(320.000),
x(112.000),y(-112.000),z(-160.000) },
--X3
{ x(-144.000),y(-32.000),z(128.000),
x(304.000),y(-128.000),z(32.000) },
--Y3
{ x(32.000),y(144.000),z(128.000),
x(128.000),y(-304.000),z(32.000) },
--Z3
{ x(32.000),y(-32.000),z(304.000),
x(128.000),y(-128.000),z(-144.000) },
--X4
{ x(-128.000),y(-16.000),z(144.000),
x(288.000),y(-144.000),z(16.000) },
--Y4
{ x(16.000),y(128.000),z(144.000),
x(144.000),y(-288.000),z(16.000) },
--Z4
{ x(16.000),y(-16.000),z(288.000),
x(144.000),y(-144.000),z(-128.000) },
--X5
{ x(-112.000),y(0.000),z(160.000),
x(272.000),y(-160.000),z(0.000) },
--Y5
{ x(0.000),y(112.000),z(160.000),
x(160.000),y(-272.000),z(0.000) },
--Z5
{ x(0.000),y(0.000),z(272.000),
x(160.000),y(-160.000),z(-112.000) },
--X6
{ x(-96.000),y(16.000),z(176.000),
x(256.000),y(-176.000),z(-16.000) },
--Y6
{ x(-16.000),y(96.000),z(176.000),
x(176.000),y(-256.000),z(-16.000) },
--Z6
{ x(-16.000),y(16.000),z(256.000),
x(176.000),y(-176.000),z(-96.000) },
--X7
{ x(-80.000),y(32.000),z(192.000),
x(240.000),y(-192.000),z(-32.000) },
--Y7
{ x(-32.000),y(80.000),z(192.000),
x(192.000),y(-240.000),z(-32.000) },
--Z7
{ x(-32.000),y(32.000),z(240.000),
x(192.000),y(-192.000),z(-80.000) },
--X8
{ x(-64.000),y(48.000),z(208.000),
x(224.000),y(-208.000),z(-48.000) },
--Y8
{ x(-48.000),y(64.000),z(208.000),
x(208.000),y(-224.000),z(-48.000) },
--Z8
{ x(-48.000),y(48.000),z(224.000),
x(208.000),y(-208.000),z(-64.000) },
}
LIBS = $(SUBLIBS) -L/usr/lib/x86_64-linux-gnu -L/usr/X11R6/lib64 -lQtOpenGL -lQtGui -lQtCore -lGL -lpthread -lGLU -lpng
-lQtOpenGL -lGL -lpthread -lGLU -lpng
sapier wrote:ohhh I see did you specify a name for the box? It won't be added to list without having an identifier (name).
sapier wrote:No it doesn't nodebox drawing requires min/max to be correct or your boxes won't be shown correctly in minetest...
ok ok an error message would be nice to let user know whats wrong. But wim is a quick and dirty solution with only basic error checking. I'll add it in one of the following releases.
Rubenwardys editor most likely will be more user-friendly when its done.
sapier wrote:Yes but there's a texture bug if your model exceeds node size -50 <-> + 50 I didn't have time to look for it by now
GLWidget.cpp: In Elementfunktion »void GLWidget::loadTexture(QString, int)«:
GLWidget.cpp:240:40: Fehler: »class QString« hat kein Element namens »toAscii«
bool success = loadPngImage(filename.toAscii().data(), width, height, hasAlpha, &this->m_texture_data[number]);
Users browsing this forum: No registered users and 2 guests