TPT "Megabuilds" Suggestion
-
TPT Megabuilds would be an alternate program similiar to TPT Legacy but is designed with the sole purpose of having more room in the simulation to do whatever, for those people who just don't have enough room for their various creations.
Pros:
More space for simulations
Cons:
Incompatible with regular TPT saves
Possibly unstable (Read in a similiar help thread)
Lower FPS
I Know this has less pros then cons but I mentioned that it would be an alternate file similiar to legacy, not TPT itself.
Any Critiscm and ideas appreciated.
-
This post is hidden because the user is banned
-
Quote from jacob1:
this is not possible at all. Every save ever made has had the same resolution, and that is defined as a constant used all over the game in many places (XRES and YRES). Even making this variable able to be changed causes a lot of problems, because you have to delete the current simulation, save renderer, and other things and create new ones every time a save has a different resolution. Also many interfaces look bad at larger sizes, because they weren't designed for it. It also causes a lot of lag having it a variable, and many people wouldn't be able to open larger saves because their computers are too slow, and they have small screens.
So we can't really do this, it requires rewriting a lot of things and a lot of work, and it would be too laggy for most people. -
It would be possible to make a larger sized version (just the interface would have to be modified a little), but I don't know where you would be able to save the saves you made with it, since it can't be on the save server with everything else because of incompatibility issues.
It would be able to open smaller saves just fine, but they would be in the top right corner and it would cause a few problems on the edges ...
But making XRES and YRES changeable is not a good idea and not something I want to try to do, if anything, just for the lag caused on some computers. It technically is possible now (I think, there still might be some challenges), but all of the reasons in that post above are the reasons I don't really want to do it, there are better things to work on. -
Resizing the screen? I've done it in seconds; No total ground-up recode.
-
-
I believe that a variable size is actually a good idea. There's nothing "game-breaking" about it. I see no reason why this couldn't be implemented properly:
Starting a new creation:
This is where it should specify how big you want the playing field to be.
Click on [New], a small dialog box pops up asking for width/height sizes.
It could be possible to be able change the size of the field, but then may have to be some hacking and slashing in the source (and that's no good.)
Saving/Loading saves of variable sizes:
Saves should store the size the window used for the creation, so that when a player loads a save, it should automatically size it to the save's require size.
Dealing with small screens:
An issue arises when a player tries to load a save that is larger than his/her screen resolution. I believe the solution is simple; to set a limit on just how large you can set the field size.
I believe 800x600 should be the maximum size, after all, who today uses a monitor that is any smaller than that?
I also believe this maximum size is appropriate because any field size bigger than that would likely cause unacceptable lag issues.
I honestly can't find any reasons why this couldn't be implemented. What do you guys think
-
This post is hidden because the user is banned
