Try out LodePaint!
Hi,
I made a painting program, called "LodePaint". It's not finished yet, but quite usable and it would be nice if someone could test it on various computers.
Here's the Windows version: http://members.gamedev.net/lode/projects/LodePaint_Win32.zip
Here's the Linux version: http://members.gamedev.net/lode/projects/LodePaint_Linux.zip
The readme.txt contains all info you need! Except how to install it:
Windows: Unzip the zip and run the exe
Linux: Unzip the zip, make "lodepaint" executable, and run ./lodepaint from a terminal
Needs SDL and OpenGL.
Please let me know if it works and how you think its state is so far!
[Edited by - Lode on December 13, 2009 3:45:17 PM]
It works nicely for me (32-bit Vista Business, ATi Radeon HD 3450). It's pleasant to use, though I'm not much of an artist. [smile] It would be nice if drawing operations were clipped to the current selection rectangle, though, and you can set the brush's "softness" value to one that has too many decimal places for the form to display if you use the slider (numbers appear to the right of the spinner - maybe a percentage would be a more appropriate?) Great stuff so far!
[Website] [+++ Divide By Cucumber Error. Please Reinstall Universe And Reboot +++]
I downloaded it earlier before you yanked it back down. Any differences?
The key things I noticed were -
* Lack of hotkeys. No Ctrl+Z for undo. Ack.
* This program is begging to be a slick pixel editor. A toggleable grid partitioning pixels would be handy.
* No dynamic changin of brush size. Being able to hold down a key + scroll wheel and adjusting a brush size on the fly is a good thing to have.
I didn't play with it for very long, but I noticed those. [wink]
The key things I noticed were -
* Lack of hotkeys. No Ctrl+Z for undo. Ack.
* This program is begging to be a slick pixel editor. A toggleable grid partitioning pixels would be handy.
* No dynamic changin of brush size. Being able to hold down a key + scroll wheel and adjusting a brush size on the fly is a good thing to have.
I didn't play with it for very long, but I noticed those. [wink]
laziness is the foundation of efficiency | www.AdrianWalker.info | Adventures in Game Production | @zer0wolf - Twitter
Works well on ubuntu (karmic). One issue I had was that the color and global tool settings controls were cut off, so I had to move them to a different place on the screen. Also, if I zoomed in a lot, the guide that shows where a pixel will be placed extended beyond the drawing pane (see this). Otherwise, it's a nifty paint program. Good work.
--------------------Enigmatic Coding
Quote: Original post by zer0wolf
I downloaded it earlier before you yanked it back down. Any differences?
Yeah the earlier version could crash sometimes while drawing.
Quote: Original post by zer0wolf
* No dynamic changin of brush size. Being able to hold down a key + scroll wheel and adjusting a brush size on the fly is a good thing to have.
I like that idea :)
Quote: Works well on ubuntu (karmic). One issue I had was that the color and global tool settings controls were cut off, so I had to move them to a different place on the screen.
By default the screen takes a resolution of 1024*768 pixels, but this can be changed in the config file ~/.config/lpi/LodePaint/settings.txt (in Windows it's under Application Data). That could have an influence depending on the desktop resolution.
Won't run for me - hangs during start-up on my Acer (GT 240M, 4Gb RAM, etc), Vista home premium...
Not sure, but it seems to take up a bunch of resources and then falls into an infinite loop. The main window gets created and the cursor changes, but then it hangs and becomes unresponsive.
edit: Which is a bummer because I alteady uninstalled Photoshop 8(
Not sure, but it seems to take up a bunch of resources and then falls into an infinite loop. The main window gets created and the cursor changes, but then it hangs and becomes unresponsive.
edit: Which is a bummer because I alteady uninstalled Photoshop 8(
Quote: Original post by irreversible
Won't run for me - hangs during start-up on my Acer (GT 240M, 4Gb RAM, etc), Vista home premium...
Not sure, but it seems to take up a bunch of resources and then falls into an infinite loop. The main window gets created and the cursor changes, but then it hangs and becomes unresponsive.
edit: Which is a bummer because I alteady uninstalled Photoshop 8(
Is the vista 32-bit or 64-bit?
Is there anything visible on the main window, and what does the cursor change into?
Does this game here work? http://members.gamedev.net/lode/games/torenoorlog/Torenoorlog_20071212.zip. It uses the same engine (SDL + OpenGL).
Thanks.
Blah... Yes, feedback. I started playing the damn game. I always get addicted when playing TD.
In any case - the game works nicely. Could use better controls, but works nicely :)
The paint program freezes as soon as the window is created. The cursor changes to a black arrow when the mouse hovers above the window, so I'm guessing a SetCursor() command is reached. Nothing visible in the main window except a black background.
Vista 32 with all service packs and stuff.
In any case - the game works nicely. Could use better controls, but works nicely :)
The paint program freezes as soon as the window is created. The cursor changes to a black arrow when the mouse hovers above the window, so I'm guessing a SetCursor() command is reached. Nothing visible in the main window except a black background.
Vista 32 with all service packs and stuff.
So... when is the next version of LodePaint coming? [wink]
laziness is the foundation of efficiency | www.AdrianWalker.info | Adventures in Game Production | @zer0wolf - Twitter
Quote: Original post by zer0wolf
So... when is the next version of LodePaint coming? [wink]
It's always progressing in small steps. I updated the Windows link in the original post (Linux version follows later) with a newer version.
There aren't any spectacular changes, some small user experience enhancements, an options dialog, previews in some of the filter dialogs, and fixed some memory leaks by using valgrind. And the manual is HTML with screenshots now.
But another change is that it'll now spit out some console output! In the Windows version this output goes to a file "stdout.txt" next to the executable because that's for some reason what SDL does in Windows when using Dev-C++. And this console output can be used to find out why exactly it hangs or crashes at startup. If all goes well, the output should be like this:
PaintDebug Info: Starting LodePaintPaintDebug Info: Loading persistent dataPaintDebug Info: Persistent data loadedPaintDebug Info: Creating screeninfo: initing SDLinfo: SDL initedinfo: initing screeninfo: screen initedinfo: initing GLinfo: GL initedPaintDebug Info: Screen created. Creating gui drawerPaintDebug Info: Gui drawer created. Creating main containerPaintDebug Info: Main container createdPaintDebug Info: Starting main loopPaintDebug Info: Program finished successfully
If someone has problems with starting it up, where exactly does the output end? Thanks! So you should find the output in stdout.txt in the folder where the executable is, if there's no stdout.txt to be found at all then either Windows gives no permissions to write in that folder and it should be run as admin or from a folder with permissions, or, something is so screwed up that it crashes before even starting the main function.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement