Its really a great idea and you should really work on it =P
VB is a great program to begin doing this little programs, but i dont actually know if it supports 3D, does it?
I search what was XNA and it looks a great program =D
Edit:
Here are some opening tests i did =D and first let me tell my computer Specs:
Graphic board - Nvidia Geforce 275
CPU - Intel i7
Ram - 6gbs
(Running in normal speed, not overclock or underclock)
Tests:
1x1 grid (1 layer) - Less then 1 second
10x10 grid (1 layer) - Less then 1 second
50x50 grid (1 layer) - 15 seconds
100x100 grid (1 layer) - 2 minutes and 56 seconds
200x200 grid (1 layer) and 50x50 (100 layers) - It did a complete crash on my computer =S i need to wait like 1 minute then the program closes it self and my computer goes to normal again, here is a picture of the cpu and ram:
Here are some opening tests i did =D and first let me tell my computer Specs:
Graphic board - Nvidia Geforce 275
CPU - Intel i7
Ram - 6gbs
(Running in normal speed, not overclock or underclock)
Tests:
1x1 grid (1 layer) - Less then 1 second
10x10 grid (1 layer) - Less then 1 second
50x50 grid (1 layer) - 15 seconds
100x100 grid (1 layer) - 2 minutes and 56 seconds
200x200 grid (1 layer) and 50x50 (100 layers) - It did a complete crash on my computer =S i need to wait like 1 minute then the program closes it self and my computer goes to normal again, here is a picture of the cpu and ram:
Yeah, I'm not sure when I'll have the optimization done, but maybe you could run your tests again after? It would be nice to see a comparison.
[Edit] And to anyone who might actually be waiting for this to be more usable, sorry, I know it's taking a while, but I'm a full time student, among other things. Throw in a minecraft addiction with everything else, and projects grow neglected :tongue.gif: I'm also partially waiting on a reply from someone who's giving me a hand with everything, they have significantly more VB experience than myself.
Rollback Post to RevisionRollBack
If someone spams or trolls your thread...don't get angry with them. Thank them. They just gave you a free bump.
Sure i can run the tests after =D and if you need something more just tell me =P
Edit: Btw this is the best program to make a maze!!!!! like i was thinking of something to do and then i realize that this is rly helpful to make mazes!!!!!
Sure i can run the tests after =D and if you need something more just tell me =P
Edit: Btw this is the best program to make a maze!!!!! like i was thinking of something to do and then i realize that this is rly helpful to make mazes!!!!!
Omg...mazes...yes!
Rollback Post to RevisionRollBack
If someone spams or trolls your thread...don't get angry with them. Thank them. They just gave you a free bump.
The install worked like a :wink.gif: Thanks! Nifty little program, can't wait for it to be developed further.
Let me know if you have any problems, other than it being slow(I know it's slow right now, I'll be open to complaints about speed again as soon as optimizations are done :tongue.gif: ).
I'm glad this is being received well. As soon as optimization, file saving, and forum bbcode outputs are finished...I have a crafty little plan that goes along with the program :tongue.gif: Details to come either when I feel like it, or I'm ready to release...I suppose those are the same thing, or seem that way...but meh, they seem different in my head.
Rollback Post to RevisionRollBack
If someone spams or trolls your thread...don't get angry with them. Thank them. They just gave you a free bump.
Here is a little help on a little thing =D
If you check the icon on the left Corner, rly near the name, the icon that you have right now is the default one, if you check the properties of your MC planner Window, you can change the icon, but it only works with .Ico images.
I only know a little of visual basic, and that would be a little upgrade.
Here is a little help on a little thing =D
If you check the icon on the left Corner, rly near the name, the icon that you have right now is the default one, if you check the properties of your MC planner Window, you can change the icon, but it only works with .Ico images.
I only know a little of visual basic, and that would be a little upgrade.
Yeah...I was aware of that, I'm just lazy. I've been putting off most of the beautification type things in order to put all my time and effort on the project into the core features. Now that everything else is falling into place, I need to step back and actually put in icons, better UI, etc etc. Blame my laziness :tongue.gif:
Rollback Post to RevisionRollBack
If someone spams or trolls your thread...don't get angry with them. Thank them. They just gave you a free bump.
Here is a little help on a little thing =D
If you check the icon on the left Corner, rly near the name, the icon that you have right now is the default one, if you check the properties of your MC planner Window, you can change the icon, but it only works with .Ico images.
I only know a little of visual basic, and that would be a little upgrade.
Yeah...I was aware of that, I'm just lazy. I've been putting off most of the beautification type things in order to put all my time and effort on the project into the core features. Now that everything else is falling into place, I need to step back and actually put in icons, better UI, etc etc. Blame my laziness :tongue.gif:
The latency for the crunching seems way off. How are you saving the instances of the layers? They should really all just be an instance of a base class.
Made your base layer class with attributes for width and height.
Create your layer classes while inheriting the base class, this should allow you to have them all use the same width and height constants preventing you from having to define them with every instance.
Traversing through the layers could be handled by calling a 'clear/draw' function that outputs the layer into the picture element.
Since the class is kept in memory, recall shouldn't take long at all.
Maybe you've already pushed them into classes... but if not, I would consider making them now to help you in the future.
Edit:
This also crossed my mind, but you could save on memory by creating a 'new layer' button that would spawn the new instance of the class, along with an 'Up' and 'Down' button...
That way the user is only creating layers that he is using. You could even thrown in a 'delete layer' function to drop the instance.
Here is a little help on a little thing =D
If you check the icon on the left Corner, rly near the name, the icon that you have right now is the default one, if you check the properties of your MC planner Window, you can change the icon, but it only works with .Ico images.
I only know a little of visual basic, and that would be a little upgrade.
Yeah...I was aware of that, I'm just lazy. I've been putting off most of the beautification type things in order to put all my time and effort on the project into the core features. Now that everything else is falling into place, I need to step back and actually put in icons, better UI, etc etc. Blame my laziness :tongue.gif:
The latency for the crunching seems way off. How are you saving the instances of the layers? They should really all just be an instance of a base class.
Made your base layer class with attributes for width and height.
Create your layer classes while inheriting the base class, this should allow you to have them all use the same width and height constants preventing you from having to define them with every instance.
Traversing through the layers could be handled by calling a 'clear/draw' function that outputs the layer into the picture element.
Since the class is kept in memory, recall shouldn't take long at all.
Maybe you've already pushed them into classes... but if not, I would consider making them now to help you in the future.
Edit:
This also crossed my mind, but you could save on memory by creating a 'new layer' button that would spawn the new instance of the class, along with an 'Up' and 'Down' button...
That way the user is only creating layers that he is using. You could even thrown in a 'delete layer' function to drop the instance.
The main problem right now is that the program was initially a quick and dirty mock up using picture boxes(each square of the grid is a separate picture, this results in every single one having all the inherited properties and controls of a picture box...instant memory hog). I'm moving away from those, as well as some change up in the overall structure of how the grids are created and accessed. Having height and width properties is somewhat redundant due to the images in the resource file already being the correct width and height-however this could change, in any case, it will be treated as a constant 16x16.
I already have the grid properties contained within a "GridBlock" class, and will probably be heavily reworking it in the next little while.
I like your "new layer" suggestion. I think it's more intuitive, while also being a little bit easier on load times and memory usage. I'll probably go that route.
[Edit] The person who I mentioned earlier that's directly helping me with the optimization end of things has sent me his suggestions. Hopefully tonight or tomorrow I'll be ready to send out the optimized version :smile.gif:
[Edit2] So...much...learning o.o
Rollback Post to RevisionRollBack
If someone spams or trolls your thread...don't get angry with them. Thank them. They just gave you a free bump.
How are you loading your images? Separate files or are you creating sprites from one image? If you aren't using sprites, I would recommend them as you can use DrawImage() to output just the 16x16 chunk.. or 32... if you stick with the standard texture files, you could even make it possible for users to use their own texture packs.
Tab order is off since you added the Layer input on your initial 'New Grid' GUI.
Here are some suggestions I had while dealing with it.
If you thread it, you can have your mouse actions over the graphic object be captured, that way you can click and hold to draw instead of clicking for each square.
You may also want to consider dropping the 'Air' block inside the selection dialog and just make right click 'delete/air block'
Block selection and layer selection could really be their own non-modal containers. So the user can have them up and move them where they want.
A checkbox for 'Overview' that would read the layers from the bottom up and replacing anything that isn't an air block (should probably render the graphic uneditable while it is checked). This would create a nice top-down view for the user. The same concept could be applied to any side view, as long as you are reading in the graphic from the layer that is farthest from the 'camera', it should give a good view of what it will look like.
Haven't done much work on it. School and other life related things are pushing this fairly low down on the priority list. I'm not halting working on it, I just gotta find the time somewhere.
Rollback Post to RevisionRollBack
If someone spams or trolls your thread...don't get angry with them. Thank them. They just gave you a free bump.
I for one am still interested in this. Need a good schematic program still. Optimizations would be pretty good as I don't have nearly the amount of RAM your helper does. x.x
VB is a great program to begin doing this little programs, but i dont actually know if it supports 3D, does it?
I search what was XNA and it looks a great program =D
Edit:
Here are some opening tests i did =D and first let me tell my computer Specs:
Graphic board - Nvidia Geforce 275
CPU - Intel i7
Ram - 6gbs
(Running in normal speed, not overclock or underclock)
Tests:
1x1 grid (1 layer) - Less then 1 second
10x10 grid (1 layer) - Less then 1 second
50x50 grid (1 layer) - 15 seconds
100x100 grid (1 layer) - 2 minutes and 56 seconds
200x200 grid (1 layer) and 50x50 (100 layers) - It did a complete crash on my computer =S i need to wait like 1 minute then the program closes it self and my computer goes to normal again, here is a picture of the cpu and ram:
I'll continue working on it, and I'll honestly just be figuring things out as I go along. One step at a time is good.
Yeah thats fine and you are just starting =D
Yeah, I'm not sure when I'll have the optimization done, but maybe you could run your tests again after? It would be nice to see a comparison.
[Edit] And to anyone who might actually be waiting for this to be more usable, sorry, I know it's taking a while, but I'm a full time student, among other things. Throw in a minecraft addiction with everything else, and projects grow neglected :tongue.gif: I'm also partially waiting on a reply from someone who's giving me a hand with everything, they have significantly more VB experience than myself.
Edit: Btw this is the best program to make a maze!!!!! like i was thinking of something to do and then i realize that this is rly helpful to make mazes!!!!!
Omg...mazes...yes!
Let me know if you have any problems, other than it being slow(I know it's slow right now, I'll be open to complaints about speed again as soon as optimizations are done :tongue.gif: ).
I'm glad this is being received well. As soon as optimization, file saving, and forum bbcode outputs are finished...I have a crafty little plan that goes along with the program :tongue.gif: Details to come either when I feel like it, or I'm ready to release...I suppose those are the same thing, or seem that way...but meh, they seem different in my head.
If you check the icon on the left Corner, rly near the name, the icon that you have right now is the default one, if you check the properties of your MC planner Window, you can change the icon, but it only works with .Ico images.
I only know a little of visual basic, and that would be a little upgrade.
Yeah...I was aware of that, I'm just lazy. I've been putting off most of the beautification type things in order to put all my time and effort on the project into the core features. Now that everything else is falling into place, I need to step back and actually put in icons, better UI, etc etc. Blame my laziness :tongue.gif:
The latency for the crunching seems way off. How are you saving the instances of the layers? They should really all just be an instance of a base class.
Made your base layer class with attributes for width and height.
Create your layer classes while inheriting the base class, this should allow you to have them all use the same width and height constants preventing you from having to define them with every instance.
Traversing through the layers could be handled by calling a 'clear/draw' function that outputs the layer into the picture element.
Since the class is kept in memory, recall shouldn't take long at all.
Maybe you've already pushed them into classes... but if not, I would consider making them now to help you in the future.
Edit:
This also crossed my mind, but you could save on memory by creating a 'new layer' button that would spawn the new instance of the class, along with an 'Up' and 'Down' button...
That way the user is only creating layers that he is using. You could even thrown in a 'delete layer' function to drop the instance.
Lulz
The main problem right now is that the program was initially a quick and dirty mock up using picture boxes(each square of the grid is a separate picture, this results in every single one having all the inherited properties and controls of a picture box...instant memory hog). I'm moving away from those, as well as some change up in the overall structure of how the grids are created and accessed. Having height and width properties is somewhat redundant due to the images in the resource file already being the correct width and height-however this could change, in any case, it will be treated as a constant 16x16.
I already have the grid properties contained within a "GridBlock" class, and will probably be heavily reworking it in the next little while.
I like your "new layer" suggestion. I think it's more intuitive, while also being a little bit easier on load times and memory usage. I'll probably go that route.
[Edit] The person who I mentioned earlier that's directly helping me with the optimization end of things has sent me his suggestions. Hopefully tonight or tomorrow I'll be ready to send out the optimized version :smile.gif:
[Edit2] So...much...learning o.o
Tab order is off since you added the Layer input on your initial 'New Grid' GUI.
Here are some suggestions I had while dealing with it.
If you thread it, you can have your mouse actions over the graphic object be captured, that way you can click and hold to draw instead of clicking for each square.
You may also want to consider dropping the 'Air' block inside the selection dialog and just make right click 'delete/air block'
Block selection and layer selection could really be their own non-modal containers. So the user can have them up and move them where they want.
A checkbox for 'Overview' that would read the layers from the bottom up and replacing anything that isn't an air block (should probably render the graphic uneditable while it is checked). This would create a nice top-down view for the user. The same concept could be applied to any side view, as long as you are reading in the graphic from the layer that is farthest from the 'camera', it should give a good view of what it will look like.
Lulz
Haven't done much work on it. School and other life related things are pushing this fairly low down on the priority list. I'm not halting working on it, I just gotta find the time somewhere.
Oh, and if life gives you more lemons, make Chocolate Rain!