Spring RTS Engine

I'd like to suggest their be an easy way to rotate the camera angle of a map by 90 degrees with a short key when playing with the standard camera mode, it would make maps more interesting to me personally as i would be able to see them from angles that i normally would never see without speccing and using other camera modes.


tl;dr spice maps up by making the default camera turn by 90 degrees by using a keybind such as ctrl [ or ] for instances.

could it be a feature though, instead of a lua and a meta key?

Spawn_Retard wrote:could it be a feature though, instead of a lua and a meta key?

All cameras should eventually be moved to lua.

Regret wrote:

Spawn_Retard wrote:could it be a feature though, instead of a lua and a meta key?

All cameras should eventually be moved to lua.

And what do users see if luaui crashes?

Google_Frog wrote:And what do users see if luaui crashes?

One default engine camera.

Regret wrote:

Google_Frog wrote:And what do users see if luaui crashes?

One default engine camera.

BINGO

i think the rotating would be very useful.It might be even added to TA-style overview camera because rotation is the only thing taht this cam mode lacks.
That could be the "default engine camera".

Regret wrote:

Spawn_Retard wrote:could it be a feature though, instead of a lua and a meta key?

All cameras should eventually be moved to lua.

http://springrts.com/phpbb/viewtopic.ph ... 67#p397067

hypocrisy much?
let me paraphrase it here, changes marked italic

Regret wrote:a) having new widget is good
b) losing a feature from engine for no reason (cameras do not prohibit anything while being an engine feature) despite having a widget replacement is bad
c) having both the widget AND the current engine feature is better than having just a widget

engine fixes are always better than widgets, because widgets lose compatability between spring versions

Brain Damage wrote:

Regret wrote:

Spawn_Retard wrote:could it be a feature though, instead of a lua and a meta key?

All cameras should eventually be moved to lua.

http://springrts.com/phpbb/viewtopic.ph ... 67#p397067

hypocrisy much?
let me paraphrase it here, changes marked italic

Regret wrote:a) having new widget is good
b) losing a feature from engine for no reason (cameras do not prohibit anything while being an engine feature) despite having a widget replacement is bad
c) having both the widget AND the current engine feature is better than having just a widget

no u

Changing words is very mature, even if you point out what you changed, it deforms the original point which was specific to the thread.

This is completely different as current camera system conflicts with additional lua cameras, so one has to go or a new system has to be made for both to function together.

My request: engine support for rotating the minimap. Rotating the minimap in Lua means re-implementing a farktonne UI stuff, the kind of thing that will break between versions. With rotatable minimap, the rotatable cameras will be much more usable.

Pxtl wrote:My request: engine support for rotating the minimap. Rotating the minimap in Lua means re-implementing a farktonne UI stuff, the kind of thing that will break between versions. With rotatable minimap, the rotatable cameras will be much more usable.

+1

Even /viewtaflip does not flip minimap.

Pxtl wrote:My request: engine support for rotating the minimap. Rotating the minimap in Lua means re-implementing a farktonne UI stuff, the kind of thing that will break between versions. With rotatable minimap, the rotatable cameras will be much more usable.

+1

there is a subforum somewhere i think.

Rotating the minimap in Lua means re-implementing a farktonne UI stuff, the kind of thing that will break between versions. With rotatable minimap, the rotatable cameras will be much more usable.

Not really. You can just screen-cap it, store it a texture, put it on a quad, rotate it. Which is pretty much all you'd want to do in the engine to flip it.

It'd be better to open the engine up more, so that it's easier to implement a custom minimap, imo.

Argh wrote:Not really. You can just screen-cap it, store it a texture, put it on a quad, rotate it. Which is pretty much all you'd want to do in the engine to flip it.

It'd be better to open the engine up more, so that it's easier to implement a custom minimap, imo.

Easier said than done, it's quite hard to remake the engine minimap in lua in current Spring.

What's the problem? When DrawInMiniMap() operates, the minimap's already drawn.

Get the relative position of that, and capture that portion of the framebuffer in a bitmap (to see how to create a bitmap in Spring, read the P.O.P.S. source, it's really easy). By definition, it won't capture the quad you drew last DrawInMiniMap(), if you do the capture operation first, because it hasn't been drawn yet.

Then put that bitmap on a TexRect, rotate it 90 degrees, and voila. Perfect rotation. Now, will all the icons be "right side up"? No. But it will work, and it's pretty easy.

Meh, wish I wasn't so busy atm, this really is pretty straightforward OpenGL. Doing something more complicated... not so much. Google "how to capture screen OpenGL".

Argh wrote:What's the problem? When DrawInMiniMap() operates, the minimap's already drawn.

Get the relative position of that, and capture that portion of the framebuffer in a bitmap (to see how to create a bitmap in Spring, read the P.O.P.S. source, it's really easy). By definition, it won't capture the quad you drew last DrawInMiniMap(), if you do the capture operation first, because it hasn't been drawn yet.

Then put that bitmap on a TexRect, rotate it 90 degrees, and voila. Perfect rotation. Now, will all the icons be "right side up"? No. But it will work, and it's pretty easy.

And then recreate unit selection through minimap, giving orders etc.

How would you do that?

Offset the orders / attempts. If you rotate it... X becomes Y, or negative X / negative Y, if an order's passed and mouse is within the bounds of the minimap.

Argh wrote:Offset the orders / attempts. If you rotate it... X becomes Y, or negative X / negative Y, if an order's passed and mouse is within the bounds of the minimap.

What about custom formation widget drawing order lines on minimap?