Forums » General
Changelog:
*** Vendetta 1.8.417
- New Hornet graphical ship assets for Android.
- Added "Designate Enemy" option in the Target HUD menu. It tags the
currently selected ship as an enemy when pressed.
- Added optional larger HUD touch regions on Android and default to
using it on phone-scale devices.
- Touchscreen analog (left) throttle/strafe region now uses linear
input for more rapid response.
- Touchscreen analog (right) orientation input now defaults to an
improved "vector cube root" curve.
- Multiple input curve options now available for both touchscreen
analog regions.
- Touch input regions now use linked X-and-Y axes for more uniform
sensitivity.
- Disabled input filtering for touchscreen devices, with options to
re-enable.
- Touch tracking circles are now drawn in the HUD touch regions.
- New "flight/strafe" tutorial back-propagated from "HD" version to
regular Android release.
- All Android versions now default to the Platinum UI skin.
- Android non-VR font now defaults to NTR-Regular.
- Removed un-needed "Use UI With Head Tracking" option for Gear VR and
Daydream.
- Worked around device problem on Mali-G71-based devices, such as
"international" versions of Samsung Galaxy S8 and S8+.
*** Vendetta 1.8.417
- New Hornet graphical ship assets for Android.
- Added "Designate Enemy" option in the Target HUD menu. It tags the
currently selected ship as an enemy when pressed.
- Added optional larger HUD touch regions on Android and default to
using it on phone-scale devices.
- Touchscreen analog (left) throttle/strafe region now uses linear
input for more rapid response.
- Touchscreen analog (right) orientation input now defaults to an
improved "vector cube root" curve.
- Multiple input curve options now available for both touchscreen
analog regions.
- Touch input regions now use linked X-and-Y axes for more uniform
sensitivity.
- Disabled input filtering for touchscreen devices, with options to
re-enable.
- Touch tracking circles are now drawn in the HUD touch regions.
- New "flight/strafe" tutorial back-propagated from "HD" version to
regular Android release.
- All Android versions now default to the Platinum UI skin.
- Android non-VR font now defaults to NTR-Regular.
- Removed un-needed "Use UI With Head Tracking" option for Gear VR and
Daydream.
- Worked around device problem on Mali-G71-based devices, such as
"international" versions of Samsung Galaxy S8 and S8+.
Lot of mobile updates here. Thanks for working hard on the game and pushing these updates through. Though would be nice to see a Goliath manu mission pushed out. (On Oct 31st they should be called Ghouliaths and have a haunting engine sound).
Oh a Halloween treat would be awesome
Developers++!
- Added "Designate Enemy" option in the Target HUD menu. It tags the
currently selected ship as an enemy when pressed.
Will we have a "designate friendly" version too? Even if it were just a /command I would like that. Tired of all my buddies swarming my radar in red :P
- Added "Designate Enemy" option in the Target HUD menu. It tags the
currently selected ship as an enemy when pressed.
Will we have a "designate friendly" version too? Even if it were just a /command I would like that. Tired of all my buddies swarming my radar in red :P
Even if it were just a /command I would like that.
Target someone or something and then typing /designateenemy works.
Target someone or something and then typing /designateenemy works.
Devs... Wow. /applaud
These chanages going to get pushed through to regular gamepad analog sticks eventually?
These chanages going to get pushed through to regular gamepad analog sticks eventually?
How long does the enemy designation stick?
Glad you guys like the release. Also:
- I am working on the Goliath, but there were too many other-things-needing-Q/A for me to get it out this week. The whole Galaxy S8 debacle and other issues have been.. time consuming.
- These mobile changes are also directly related to shipping on iPhone, FWIW. Easier to prototype all the design changes and test them on Android in advance. The "regular" sized iPhones are.. small, which is challenging from a gameplay standpoint.
- We have a whole new config UI and feature set for PC gamepads that has been intended for release for some time. But, it keeps getting delayed. The PC is also a little challenging, due to varying APIs and standards (even on Windows.. DirectInput vs Xinput, etc).
- I'm.. not sure how long the enemy designation sticks. I would guess for the runtime of the client. I'll ask Ray.
- I am working on the Goliath, but there were too many other-things-needing-Q/A for me to get it out this week. The whole Galaxy S8 debacle and other issues have been.. time consuming.
- These mobile changes are also directly related to shipping on iPhone, FWIW. Easier to prototype all the design changes and test them on Android in advance. The "regular" sized iPhones are.. small, which is challenging from a gameplay standpoint.
- We have a whole new config UI and feature set for PC gamepads that has been intended for release for some time. But, it keeps getting delayed. The PC is also a little challenging, due to varying APIs and standards (even on Windows.. DirectInput vs Xinput, etc).
- I'm.. not sure how long the enemy designation sticks. I would guess for the runtime of the client. I'll ask Ray.
Woo iPhone! My SE will get to experience VO! Maybe! I thought the last one I had would get to as well and I had that one for 2 years.
I VERY much DO NOT appreciate there being silly "you are touching here" dots, on my DROIDBUTTON touch fields. Blocks the radar on the two that (were) overlaid on the radar, and obstructs other parts of the screen for touch fields that aren't over the radars.
As well as: the radars being moved which throws off my entire massive droidbutton setup, which took I don't even know how many DAYS to set up in the first place. Last time I counted there's at least 70 things I've done with droidbuttons and had it all sitting nicely on the screen, then tonight I login and the radars moved which messes allllll of that up.
Need to add options for disabling those silly dots, and whether to use the old radar positions or the new radar positions.
IMO both of these things are cases of fixing something that wasnt broke in the first place. Now that there's dots on all touch fields obstructing whatever may be behind those touch fields, and the radars moved, I'd say things certainly are broke now.
As well as: the radars being moved which throws off my entire massive droidbutton setup, which took I don't even know how many DAYS to set up in the first place. Last time I counted there's at least 70 things I've done with droidbuttons and had it all sitting nicely on the screen, then tonight I login and the radars moved which messes allllll of that up.
Need to add options for disabling those silly dots, and whether to use the old radar positions or the new radar positions.
IMO both of these things are cases of fixing something that wasnt broke in the first place. Now that there's dots on all touch fields obstructing whatever may be behind those touch fields, and the radars moved, I'd say things certainly are broke now.
xXxDSMer...if anything, the fact that you needed to use droidbuttons is a case for UI improvements. When using a plugin that remaps your UI, it's not unexpected that there will be conflicts if the UI changes. You are unlikely to get a lot of sympathy for retaining old UI elements because of old droidbuttons configurations.
Aye, like, did you miss the part where plugins arent GS-sanctioned, and anything broken through plugins is not GS's problem? Be happy we have plugins at all.
@xXxDSMer Use Mover plugin to move your radars.
Need to add options for disabling those silly dots, and whether to use the old radar positions or the new radar positions.
There are options to use the old radar positions; in development I specified that we'd have options prior to release to effectively allow anyone to "revert" to the previous layout.
I don't think there's an option to remove the dots, but that's feasible.
Understand: the dots are not there for you. We've had a serious, long-standing problem with new users, where they fail to understand that continuous contact with the analog regions is recommended, or that you can drag anywhere once you begin input on a given region. These "dots" are a good way to help illustrate that without "instruction".
There are options to use the old radar positions; in development I specified that we'd have options prior to release to effectively allow anyone to "revert" to the previous layout.
I don't think there's an option to remove the dots, but that's feasible.
Understand: the dots are not there for you. We've had a serious, long-standing problem with new users, where they fail to understand that continuous contact with the analog regions is recommended, or that you can drag anywhere once you begin input on a given region. These "dots" are a good way to help illustrate that without "instruction".
I hide my fields so and option to hide the dots would be nice. But I like the idea of them .
^ agreed
"There are options to use the old radar positions; in development I specified that we'd have options prior to release to effectively allow anyone to "revert" to the previous layout."
Where might we find this option? I looked all through the options and didn't see it (since I'm talking about android I'll go ahead and specify "advanced" options. lol)
"I don't think there's an option to remove the dots, but that's feasible."
As soon as possible would be really nice. Myself and I'd bet several others take advantage of touch fields being see through. Those dots make the fields much less see through. I'm on about a 5.2 inch screen while on my phone and screen real estate is far too valuable to have touch fields that aren't see through
Understand: the dots are not there for you. We've had a serious, long-standing problem with new users, where they fail to understand that continuous contact with the analog regions is recommended, or that you can drag anywhere once you begin input on a given region. These "dots" are a good way to help illustrate that without "instruction"."
One of the joys of coding for the masses eh? :)
---------
and on the Mover tip, thanks. I may try that but would really like to find the option to revert.
on the GS doesn't support plugins post that basically said quit whining without actually going that far: these issues are not anything to do with a plugin. It's two UI changes that I personally don't like and I'm perfectly capable and welcome to express my dislike for them, so you have yourself a wonderful day :)
Where might we find this option? I looked all through the options and didn't see it (since I'm talking about android I'll go ahead and specify "advanced" options. lol)
"I don't think there's an option to remove the dots, but that's feasible."
As soon as possible would be really nice. Myself and I'd bet several others take advantage of touch fields being see through. Those dots make the fields much less see through. I'm on about a 5.2 inch screen while on my phone and screen real estate is far too valuable to have touch fields that aren't see through
Understand: the dots are not there for you. We've had a serious, long-standing problem with new users, where they fail to understand that continuous contact with the analog regions is recommended, or that you can drag anywhere once you begin input on a given region. These "dots" are a good way to help illustrate that without "instruction"."
One of the joys of coding for the masses eh? :)
---------
and on the Mover tip, thanks. I may try that but would really like to find the option to revert.
on the GS doesn't support plugins post that basically said quit whining without actually going that far: these issues are not anything to do with a plugin. It's two UI changes that I personally don't like and I'm perfectly capable and welcome to express my dislike for them, so you have yourself a wonderful day :)
Where can i download the mover plugin?
Would it be possible to make those dots invisible by using a transparent image via a skin?