|
Suggestions Post ideas and suggestions here. |
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
give mouse users a bigger map view
you know how the camera locks onto the plane when using the mouse? I found that this means that, at times, I won't be able to see some planes that are above or below me, but if they're using the keyboard they could see me perfectly well.
This needs a change imo.. everyone should have access to the same amount of information. |
#2
|
|||
|
|||
Quote:
|
#3
|
|||
|
|||
This is actually a decent point. Let me elaborate for kb users that might not know what we're talking about:
When using kb and flying near the bottom of the map, your screen will stop scrolling down once it has reached the bottom of the map. This means that kb users can see the lower 800 pixels of map even when their plane is at the very bottom of the map. Mouse users, however, have their view locked to their plane at all times. So, a mouse user at the bottom of the map will only see 400-500 pixels above them. This same principle applies to planes at the top and sides of the map as well. Whether this imbalance is something that needs to be addressed is open to debate. However, it would be great if we could test extra mouse visibility to see how it works out. I suspect that it would make mouse control harder to use at the extremes of the screen, but without trying it out I don't know for sure. |
#4
|
|||
|
|||
There's an option to maintain the exact same field of view that keyboard players experience:
Use a text editor to open ~Altitude/config/options.xml On the line starting with <generalOptions... replace cameraCenterPolicy="IF_MOUSE" with cameraCenterPolicy="NEVER" |
#5
|
|||
|
|||
Quote:
the game would also be a bit... tedious to play with the mouse if the crosshair doesn't move with the plane, too. Last edited by peww; 09-02-2011 at 03:44 AM. |
#6
|
|||
|
|||
The next update will include a "NEVER_MOUSE" camera center policy that implements the desired behavior (camera locks to edges, mouse motion reference point remains locked to plane) for testing.
|
#7
|
|||
|
|||
awesome thanks!
|
#8
|
|||
|
|||
did i mention i love altitude
lol seriously thats amazing, thanks! |
#9
|
|||
|
|||
Thank you, Lam. It's good to have devs that listen to the community.
|
#10
|
|||
|
|||
Kind of off topic, but what does "garbagecollectonspawn=true" do?
|
#11
|
|||
|
|||
Quote:
derp. edit: errrr garbageCollectOnSpawn="false" |
#12
|
|||
|
|||
I cannot describe how awesome you are.
|
#13
|
|||
|
|||
Please elaborate.
|
#14
|
|||
|
|||
Garbage collection is a programming concept that deals with cleanup of a process's internal memory. You probably shouldn't worry about it/mess with it if you don't know what it is.
|
#15
|
|||
|
|||
Ah, fair enough. Thanks.
|
#16
|
|||
|
|||
Kinda seems like that might make things weird sometimes, even with the cursor moving with the plane. Won't know until I try it on next patch I guess.
Personally, as I see it in my mind, I think I'd prefer keeping a screen-centered plane and just having some team colored markers indicating where keyboard users can usually see planes. (Kind of like when someone picks up the bomb off-screen in TBD) The garbage collection question has me curious, though. Does that command set to true actually schedule garbage collection for spawn as it indicates? Does that fix the sporadic fps drop everyone gets? |
|
|