Map Editor - 15.0.0

Version 15.0.0 released! This version was completely rewritten and uses a completely different method of updating, so should be much better functioning.

Delete all the .pyc files and try again. The problem is caused by your having a different version of Python than one who compiled the file originally. Ask the mailing list for faster results.

I keep getting this error:
"
Traceback (most recent call last):
File "/14.1.5/Map Editor.py", line 7, in <module>
import GL, GetTextures
ImportError: Bad magic number in /14.1.5/GL.pyc
"

I seem to get this often with arbitrary pygame games, can somebody help me out here?

v.14.1.5 released! The editing system caused an edited quad to be drawn twice, then 4 times, 8, 16, etc. This fixes that, and keeps the program running at what appears to be about 80fps.

v.14.1 released, sporting an entirely new input system! YAY!

Oh, yes, and the program doesn't rebuild the entire map each frame, just the relevant portion!

v.14.0.0 released! This version fixes all the problems described below. (Though you still need to have PyOpenGL and Pygame). This works by calling a list of display lists. Cool!

Sorry about that. I'm a one person dev. team and I don't have too much time. I must have forgotten to test saving.

1. For other users: you need a recent wxPython ; 2.6 will fail, the current stable ( 2.8.4 ) worked for me.

2. Bug report: crash at saving, file doenst save. Last line traceback:
File "map editor.py", line 179, in save
import write; write.write_to_file(quads, normals, path, dimensionx, dimensio
ny)
NameError: global name 'normals' is not defined

Dude, why you dont test your packages ?

on old xp

still got GLError err = 1281

In relation to the previous message that threw up GLError err = 1281 when trying to execute GLTexImage2D(): Older cards depend on texture sizes with dimensions equal to powers of 2 (or if they are really old, powers of 2 and square). Try changing the width and height arguments to a really small power of 2 and see if that fixes anything. This was the case for us with our pyopengl app running on a Geforce2 MX

Well, The program might not work on that OS. Note that's a "maybe" so it still could work. (There's a bunch of OS stuff in the program). Anyway, if the program runs, there's nothing to worry about.

Why does it say that I'm running an unsupported OS?

My mistake. That does not need to be done. I was recompiling every single list for every list changed... which amounts to several thousand. Only recompiling the changed lists make it at least as fast as the vertex arrays version, but far more compatible. v.13.1 released!

On my computer, at least, the display list compilation takes longer than expected, so the framerate for a map at any size drops to about 4. This is unacceptable. I'm going to have it recompile the list in a subprocess when the editing is done to fix this problem. I expect the release soon though.

I've decided that version 12 should not be released. Instead, development will continue with a new version, 13. Hopefully, v.13 will be compatible with all graphics cards (even moderately old ones), and will feature much faster everything. The plan is to use a hierarchy of display lists. This way, instead of recompiling the whole map each frame (like in a previous release), only the portion that changed will be updated. This will be easily fast enough (est. 70fps) on moderately new machines. Tell me what you think!

yes, i have everything. will try 11.1 this evening.

OK, see version 11.1. Did you get the program working?

readme mentions 'tester.py' file, which I was unable to locate. Could you pls add it?

Ah, that's better. That means your gfx system passes! Well, do you have Pygame, PyOpenGL, and NumPy?

btw: my xp is about four years old, and i haven't chaned the graphics card

you're right. i think it is the graphics card. ran the prog on brand-new windows vista with nvidia graphics card, and even though the program crashed afterward (no error message) it got past building textures.

I don't <i>think</i> that supports it either:
http://www.nvidia.com/page/pg_20040109440047.html

I get same error as pywiz32. My graphics card is GeForceFX 5200

To everybody: I am currently porting this entire thing to use Vertex Buffer Objects, which are more complicated to program, but more universally supported and faster.

It can't finish generating the data. I think the problem here is your graphics card, (see description). What kind of graphics card do you have? How new is it?

ugh... whenever i run the program (windows xp sp2 with python 2.4) it gets up to 'building textures...' and then spits out:

Traceback (most recent call last):
File "C:\Documents and Settings\Jerome.DANSCOMPUTER\Desktop\Jerome\downloads\Map Editor (11)\11\Map Editor.py", line 207, in ?
if __name__ == '__main__': main()
File "C:\Documents and Settings\Jerome.DANSCOMPUTER\Desktop\Jerome\downloads\Map Editor (11)\11\Map Editor.py", line 202, in main
load_textures()
File "C:\Documents and Settings\Jerome.DANSCOMPUTER\Desktop\Jerome\downloads\Map Editor (11)\11\Map Editor.py", line 44, in load_textures
textures = get_textures.main(textures)
File "C:\Documents and Settings\Jerome.DANSCOMPUTER\Desktop\Jerome\downloads\Map Editor (11)\11\get_textures.py", line 15, in main
GL_RGBA, GL_UNSIGNED_BYTE, QuadData )
File "C:\Python24\lib\site-packages\pyopengl-3.0.0a6-py2.4.egg\OpenGL\wrapper.py", line 1624, in __call__
File "C:\Python24\lib\site-packages\pyopengl-3.0.0a6-py2.4.egg\OpenGL\wrapper.py", line 924, in wrapperCall
GLError: GLError(
err = 1281,
description = 'invalid value',
baseOperation = glTexImage2D,
pyArgs = [
GL_TEXTURE_2D,
0,
GL_RGBA,
600,
587,
0,
GL_RGBA,
GL_UNSIGNED_BYTE,
'\x03\x19\x17\xff\x03\x19\x17\xff\x03...
],
cArgs = [
GL_TEXTURE_2D,
0,
GL_RGBA,
600,
587,
0,
GL_RGBA,
GL_UNSIGNED_BYTE,
'\x03\x19\x17\xff\x03\x19\x17\xff\x03...
],
cArguments = (
GL_TEXTURE_2D,
0,
GL_RGBA,
600,
587,
0,
GL_RGBA,
GL_UNSIGNED_BYTE,
c_void_p(193724468),
)
)

any recomendations?

Version 11 released.

I don't understand John's error. If there is a hidden module called "Settings" it should work. If you used Winzip and selected all to extract, it didn't select Settings and therefore didn't unzip it. For convenience, I've updated the app. to have all unhidden files.

Simon's error is more straightforward. Segmentation faults happen when a process tries to read from a nonexistent memory cache (in this case on your GPU). This program uses "Vertex Arrays" for speed, which are not supported on older or Voodoo cards. All this is what someone told me, though, so I could be wrong.

Incidentally, thanks for helping me get this working.

ubuntu 7.4 not 7.10 - im not runnig a beta. got python 2.5. other opengl-python things like soya3d demos work.

@everybody who has ImportError's. In the top-level directory rename everything from *pyw to *py. This got me further.

But after selecting the screen resolution, this happend. ubuntu 7.10 i368


Adding data to list for processing...
Done!
Fatal Python error: (pygame parachute) Segmentation Fault
Aborted (core dumped)

Same error.

Try downloading again. "Settings" is a hidden module. If it's not there, the download did not work right. If that doesn't fix it, let me know.

Traceback (most recent call last):
File "./MAP EDITOR.py", line 13, in <module>
import Settings
ImportError: No module named Settings

New version released, fixing the problem.

This happens when you have a .pyc file that was compiled by a different version of Python you are trying to import from. I use 2.4, though most people usually have 2.5. To fix this immediately, show all hidden files and folders and delete all of the files with .pyc extensions. Then rerun the program. I'll release a new version later today without them.

Traceback (most recent call last):
File "./MAP EDITOR.py", line 13, in <module>
import Settings
ImportError: Bad magic number in /home/xer/Desktop/10/Settings.pyc

This latest version uses vertex objects, which only are only really supported on newer GPUs, indeed that call tells the GPU to draw them. If your computer is rather old, that may explain it.

Fatal Python error: (pygame parachute) Segmentation Fault

This application has requested the Runtime to terminate it in an un
Please contact the application's support team for more information.

This happens on the call to "glDrawElements(GL_QUADS,number*4,GL_UNSIGNED_INT,array)" in draw() in main() in MAP EDITOR.py

BTW, It would be nice if your filenames didn't contain spaces, ie.(Map Editor.py = Map_Editor.py), as it is difficult to get my command prompt to locate folders/files with spaces(I am on windows)

Version 5.0.0 works with display lists which are only rebuilt after each time a quad is changed. It should be changed soon. However, for the meantime, while this thing can draw immense maps (500x500+) the speed to update the display list can be very slow. Remember for your computer's sake with square maps that each increasing unit squares. Like:
1x1 = 1
2x2 = 4
3x3 = 9
4x4 = 16
25x25 = 625
500x500 = 250,000
...so don't make your maps giant. I recommend no more than 100x100 for editing, 50x50 for optimum, though I've never noticed ANY framerate decrease for viewing at 500x500 (because of display lists).

I'm guessing it may be your system- I just tested it and it works fine. Also, what map dimensions were you trying for? My machine was made this year, but it can't handle anything over 20x20 without a noticeable drop in framerate. It's a semi-gaming machine too, so it has a good GPU and CPU. A non-graphic, randomly-generated map editor and viewer are in dev., though I don't know if anyone wants it.

http://www.mechanicalcat.net/tech/PyWeek/1/entrants/simon/
diary/News/Quido_s_Finally_Here

Either that or something else. Do other OpenGL programs work? Do you have OpenGL?

You might try TuxRacer- there's a port to windows, and it's OpenGL. If that works, so should this.

i'm using your program on win98 (yes, it can do 3d, even if it's slow) and every time I run it, is says:

Traceback (most recent call last):
File "C:\WINDOWS\Profiles\10324567\Desktop\jerome\downloads\Map_Editor\Map Editor\MAP EDITOR.py", line 342, in ?
if __name__ == '__main__': main()
File "C:\WINDOWS\Profiles\10324567\Desktop\jerome\downloads\Map_Editor\Map Editor\MAP EDITOR.py", line 340, in main
draw()
File "C:\WINDOWS\Profiles\10324567\Desktop\jerome\downloads\Map_Editor\Map Editor\MAP EDITOR.py", line 222, in draw
GL_RGBA, GL_UNSIGNED_BYTE, QuadData )
OpenGL.GL.GLerror: [Errno 1281] invalid value

Ah, yes. That would do it, wouldn't it? Thanks for catching that. New version released.

OK, I managed to get the importing working, just change:

dir='C:\\dev\\Python24\\Projects\\Map Editor\\Data'
sys.path.append(dir)

to...

sys.path.append("Data")

Alas though, I get just a clear screen that wont render(it got hung up in Object.main) but that happens to me sometimes with 3d stuff, so I wouldnt worry about it.

The program does look cool though :)

"another sugestion: PyOpenGL can be used with Numeric or Numpy" I don't use either in my program. I probably import them anyway, but they're unnecessary. If you got the same error too, that probably means something else is happening. It works flawlessly on my machine from download to execute. What version of pygame/python do you have? Most people have 2.5, but I have 2.4.

The problem with object.py is not about hiden files; it is the hardcoded data path that you use in 'map editor.py' and tester.py. You can look in the pygame cookbook the recipe for getting the apppath and derive for this the data path.

another sugestion: PyOpenGL can be used with Numeric or Numpy, and PyOpenGL is picky about the version of numeric packages, so maybe doing conditional imports with try - except would be more friendly? FYI I tried with Numeric 24.2, seems to work ok.

"Object" is a .py file in the "Data" (hidden) directory. If it's not there, that's your problem.

That's weird. I test downloaded it and it works fine. Try downloading it again.

Looks great, but got following error...

Traceback (most recent call last):
File "C:\Python25\downprogs\Map Editor\MAP EDITOR.py", line 43, in <module>
import screendimfull, surface, Object
ImportError: No module named Object