Version 1.0.0-RC2 is now available for download.

It fixes an error when only assigning a command to the long-press, and not also the short-press. There was also an issue with some touch regions not being properly removed when a command was changed. I think this has been resolved.

Where cna I download the current pluggin.

The download link is in the first post of this thread.

FYI - in latest version, not all the "test.print" or "test.debug" lines are commented out. This causes tracebacks to spit out whenever trying to use the plugin. Doing a search in main (I did a search in UI too, but don't think I found any) and commenting out (--) any lines starting with "test." fixed this, and it works nicely now.

Thanks for letting me know. I'm usually pretty good about commenting those out, and had been saving them just in case. I went ahead and removed all of the test lines. Everything appears to be in working order at this point.

Thank you draugath, this is an awesome plugin! As a noob, 'droid only user, this is an essential plugin.

One small issue I noticed: the long press on the native buttons stopped working for me after adding this plugin. ie. I can no longer change the target or mission buttons by long pressing them.

I'm using an Asus Transformer tab. I have the kb dock, but hoping DroidButtons means I don't need it.

Thanks again.

Thanks for the heads up.

I took a look at it, and I think I see what is going on. I'll have to mess around with it some more though to find a fix.

In the interim, I'd like to point out that the problem with the long-press on the default UI buttons only happens if you use the touch-to-place interface for placing new buttons. If you reload the interface (/reload with DroidButtons installed) or restart the game after using this, the long-press works again.

I have released version 1.0 release candidate 4.

This version updates the Touch-to-Place feature to work with the latest changes to the touch mechanics.

I haven't yet had a chance to properly address the loss of long-press functionality in the default UI buttons, but this can still be remedied by simply reloading the interface. You can use the /reload command to accomplish this. Be aware that the /reload is a command specific to the DroidButtons plugin, and is not available in the default game.

The first test release for the new version is up. It supports removing the default touch interface. It also supports creating touch fields like the aim region in the lower right corner.

In order to remove the default interface, you'll need to disable it in Options.

I've been tweaking the GUI some, so it likely needs some more polish too.

Just remember, I can't fix it, if I don't know about it. If you encounter a problem, please post about it in this thread.

EDIT: I should point out that the test release does change the way the button data is saved, such that a v2 save file isn't compatible with v1. A backup is made before the update is made, but even if you encounter problems with removing the default UI, I don't think you should have any issues by just not using that feature.

JUST INSTALLED 2.0. ICE crystals are now completely mirrored. ELSE ALL IS WORKING FINE. I WILL TRY MOVING BUTTONSVAROUND NEXT. Asus tablet.

mdunk, nothing that I've done should have made any impact on the way ice roids are rendered or textured. I'd be curious to see some screenshots though. In fact, I'm not seeing the same effect on my end at all.

I also just uploaded 2.0.0-a2. It provides support for a few more parameters related to the touch fields.

EDIT: Of note, there are a couple new commands that I added in for testing purposes (+LookX, +LookY, +LookPress). When you're not in a turret, +LookX and +LookY appear to behave just like Pitch and Turn. Further, the Mouselook toggles appear to be only useful while in a turret, at least at first glance.

I will at some point need to make a determination on how to best support turret aiming. For the time being, I'm more interested in what works.

Draugath,

Here's the info you requested:

{y=320,h=64,title="S-UP",font=18,command1="+StrafeUp",w=64,x=96},{y=432,font=18,title="S-DOWN",x=96,w=64,command1="+StrafeDown",h=64},{y=368,x=32,title="S-LEFT",font=18,command1="+StrafeLeft",w=64,h=64},{y=368,x=160,title="S-RIGHT",font=18,command1="+StrafeRight",w=64,h=64}

My problem is that I can't get into 1st person view in VO on my Transformer Prime tablet. I have ToggleView and ToggleCamera buttons on my screen but they don't do anything.

TIA for your help

--
Choo

I have run into a couple of issues when using the droidbuttons plugin.

1. The v2 development version does not work at all. Anytime i try and run it, when i open the game a message pops up telling me that "this version of droidbuttons has changed the way it saves and will try and back up your settings now." Then the game starts loading...forever. Never actually manages to enter the universe. If it ever did, this version may work perfectly, but I've never managed to get it to run so idk.

2. Reloading deletes all my buttons. (The db and reload button pop back up in their original locations.) Reloading, then placing buttons, and then reloading again....my buttons still all vanish.

3. If i close the game and log back in....all my buttons have vanished.

4. If i crash the game (usually by messing with my button placement)....all my buttons have vanished.

The buttons themselves usually work well while i have them, but they make the original hud buttons stop funtioning. Which i can supposedly fix by reloading....but then all my buttons vanish. :( lol.

Putting buttons in certain areas is also a no no. Like...I had the bright idea to stack my fire buttons on top of my original fire button thinking that the auto fire made it irrelevant for my primary fire button...but apparently putting fire 2 and fire 3 on top of the original fire button (the red aim on enext to the thruster buttons) makes autofire toggle off....and refuse to turn back on no matter where u try and toggle it from (chat, control panel, console).

Also, sometimes when hitting the original hud toggles while also using droid buttons, what the original buttons actually toggle may not be what it says. Like today....my activate button said activate, but....it toggled flight mode. I had to add another toggle for activate cause i couldnt find any way to get activate to actually activate.

I like the droidbuttons plugin, but it causes so many issues and takes so long to put all the buttons in that I usually delete it from my plugins. I really do want a strafeup and strafe down toggle tho so I keep reinstalling it....then rage uninstalling it when I cant make it work...lol.

I am using a galaxy tablet 7.0 and I am not sure how many of these issues are device specific. Most other plugins I have tried work just fine so I don't think its an entirely user error related problem. :)

Cle0p@tr@, I've done some preliminary investigation into the issues you've reported.

As to the buttons being deleted upon reload, I can't yet duplicate this. The only thing that I can think of that might be the issue is some sort of permissions conflict. The button data is saved to a file called "VendettaOnline/settings/<charactername>/system37643notes.txt". If VO is unable to save to this file then when you hit reload, or restart the game, it will have no button data to use to recreate anything. The "db" and "Reload" buttons are created by default when this file is not available.

I think I know what is causing the problem with v2. The simple immediate fix is to delete the file described above. This should prevent it from creating a backup and thus displaying that message. This will of course delete any buttons you have created, but it sounds like you're having issues with saving buttons anyway.

As for the issue with auto-fire, that is something I have not yet experimented with. Stacking buttons on top of each other is supported, though.

I'll be looking into these issue more, but I wanted to get back to you on my immediate findings.

EDIT: On the issue of auto-fire shutting off. What happens if you press the primary fire and secondary fire buttons on the default interface while auto-fire is engaged? The reason I ask is because DroidButtons doesn't do anything funny with the interface. I'll still test this out further.

Pressing the autofire buttons with the original interface doesn't mess anything up. And as long as I don't stick the fire buttons on top of the primary fire toggle, the droidbuttons buttons don't mess with it. Idk. It seemed weird to me to, especially cause I can stack other buttons on the original buttons without it messing anything up.

Regarding this file I am supposed to have....how do I get it? lol. I'd love to have my buttons actually save themselves. I wonder if I didn't cause the problem on accident myself because I tried to install the v2 of droidbuttons before I tried using v1. If v1 added this folder, I may have messed it all up. I DID try uninstalling and reinstalling the game, but that didn't do much of anything because I created the plugin folder manually and so uninstalling the game didn't delete my plugins. They all just automatically added themselves back in after the reinstall. I could try deleting everything and reinstalling and see if that fixes it.

I tried uninstalling everything and deleting all leftover folders then re installing and readding the plugin. Everything still autodeletes every time. Not really sure why.

Try going into the directory "VendettaOnline/settings/C|eopatra". You should see a file named "system37643notes.txt". Delete this file if it's there. If it's not there, then there might be some sort of permissions problem. I'm going to look into adding some debugging code that will hopefully help me get a better look at what's happening for you.

Ah yes....the settings folder has nothing in it at all. Guessing the problem has something to do with that. I will also guess that the touchwiz ui samsung insists on sticking on their devices is causing the problem somehow because touchwiz is evil and mucks everything up. I know the answer is probably to root my tablet....but I would probably brick it and then I would cry.

I don't think the answer is to root your tablet. It's likely just a simple permissions issue, and I can give you a test plugin that can verify specifically if this is the problem. I'm also trying to figure out how to easily check and change permissions on the folder. When I recently used the latest Astro, I saw how to check permissions, but not yet how to set them. This has interesting complications for VO in general though. If your device isn't allowing you to save the settings from DroidButtons, then it's likely you also can't save any system notes you create. Which is a problem that the devs should be looking into. Though, looking at the default interface, I'm not sure how you can even edit the system notes on Android.

EDIT:
I just performed a test on Android using a character name containing a pipe character similar to your own. It demonstrated the same problem with buttons disappearing upon reload. I was originally confused because Linux doesn't have a problem, but Android apparently does. I submitted a support ticket regarding this specific issue.

The simple fix is to start a new character. The more complicated fix is ask the devs if they'll change your name for you.

Oh joy. Lol. Starting over is not what I had planned. But maybe i will and switch factions while I'm at it. Hmmmn...

Thank you for your assistance. That is definitely not something I ever would have thought of.