- 1,325
- In the gravel trap
- RDAardvark
OK. I know I said no more updates for a bit, but the latest bug was annoying me.
So, version 0.75.59 is now up for download.
So, version 0.75.59 is now up for download.
It's perfectly clear.The second screen (what I refer to as the 'Tune' screen) validates its values from those you've input on the very first screen (the car setup screen). If the second screen will not let you change the value, then you should check the first screen for the min and max values you have for that component.
A quicktune will generate values based on the settings in the first screen. Just tested this and if I leave the first screen as all zeros, then quicktune will generate me a setup with the ride height and springs set to zero. The dampers, arb, etc will have meaningful values in them.
I hope I've understood what you are telling me. If not, please let me know what settings you are entering into the first screen so I can recreate the problem. Also, please check you are runing the latest (0.75.57) version.
It's perfectly clear.
Wanted to put a whole explanation here but running latest version and it just looks awesome, was wondering why it almost tripled in size
Thanks again for all you time making this app.
is it possible to get this app to work on our pc's?
if so what needs to be done to make it work?
Well, I was a bit surprised at the poll results: Opinion was pretty much evenly split between the 'I would pay for this' camp and the 'I want this for nothing' camp.
@ RDAardvark...
As previously mentioned, I said I would do some thinking, about how the earlier discussed "parts" could be added to your app.. (I see you are/were to go about it, yourself, so I better hurry).
Below are my thoughts, just out of my head... No offence taken, if you think they are totally useless or too messy
And no credits would be demanded, if you liked the ideas, and took off in some of those..
Taking off from a "dependency"-view, the "performance"-data entered for the car on the first page, are partly dependent on what extra-parts are fitted. That is in regard to weight, power (from engine tuning-packages, over smaller parts and to the turbos's), suspension (in regard to values for default/min/max-values) and also some tuning-options/values that would dependent on certain parts, like LCD and Tourqe Center Diff being added to the car...
My initial idea was/is to add a button on the "car"-page, to open a "parts"-page.
On this first "parts" I would like to identify the parts that affect the cars final specs the most:
Weight-packages (pre-filled droplist with 'none', stage1, stage2, stage3) and tick-boxes for ridgity, window-package and carbon-bonnet (doesn't matter with/without colour)...
Enigne tuning, with drop-list; none, stage1, 2, 3
ECU (droplist, standard or sports)
Turbo, droplist with low/med/high rev and intercooler
(if it gets VERY advanced, maybe your app could store diff. power/tourqe with different setups for that car?)
Drivetrain:
On this first page, I would also add tick-box for fittet LCD and/or CenterDiff... (maybe let tuning-page include/exclude parameters to change, in accordance with this selection?)
Transmission: Droplist (standard, 5 speed close, 6 speed close or "fully Cust. trans"
(and if any other than fully cust. trans are selected, dismiss sub-page for transmission-setting)
Suspension: Droplist (Standard, fixed sport, adjust. sport and fully adjustable)
(again according to selection, adjust possible values to enter/set on "Tune"-page.. Maybe also store different default/min/max-values, and show these values on "main"-page, and evaluate against those selected in tuning-page).
It is on purpose, that I didn't included those other parts (intake, excaust, other "drivetrain"-parts etc.) as they will have lesser influence on how the car handle, but of course power or gearchange-speeds etc...
Those was my idea, to let be added on another part-page '2' (or lower on first, by scroll), selectable with tick-boxes/droplist where appropiate...
I hope you are able to follow my thoughts...
Another small idea that came to me, was to add 2 more data-fields on the front-page.. One as an "active" field, the other for pure reference...
1: "Adjusted weight", where the extra ballast (from appropiate page) are added to the "clean" weight... (by app-calculation)
2: PP, to take a note on PerformancePoints, just for easy viewing/references..
While thinking this thru, I did get another thought, about the whole layout of the app...
Instead of those buttons, some opening a new page, other just an "in-front page", why not re-organize it into a tabbed design??
Tab-1:
From left, starting with "Car"-tab: Details about the car, make, model and year..
Small note with details about what setup and what tune are loaded (setup here refers to different parts-configuration)
Also showing the performance-data, based on the current setup and tune loaded for that car.
If possible, also showing a freetext-notesfield to that tune/setup.. (pushing it now.. i know... maybe just load those on own tap "notes")
From this tab, via the "menu"-button, there could be access to all file-actions, including load/save/delete cars, setup and tunes, import/export etc.
Tab-2:
"Parts".. containing the droplist/tick-boxes for different parts (based on my notes above).. and if needed "Parts 2" as yet a tab...
Tab-3:
Default values (like top of your current car-page) fields adjusted/loaded dependant of what setup are loaded (specially suspension and Transmission)
Tab-4:
The actual "tune-page" (with button to call "quick-tune"-routine) like current page..
Tab-5:
Tune-dependant page, containing info on varios details needed, like transmission-settings, Aero- and ballast-setting.
The 'Pros' of using a tabbed layout, in my opinion, is that you can just add extra tabs, and scroll thru them horisontally.. Then you are not constrained by the limited space on the phone... Also you could easily add or remove tabs by need or function...
But... this is just my (crazy?) thoughts, put on a piece of paper.. (or actually a screen..)
Feel free to use or ignore.. 👍
XsCodeJust tried this on my Dell Streak running Streakdroid 1.9.1, but just get Force Close every time.
AssassinTuner2.3 Android
XsCodeYou mean it won't work on 2.3 based roms?
MikaelKThe app should run on Android 2.1.x or later...
I remember it wasn't running on lower than 2.3, good to hear it's been updated.
Just tried this on my Dell Streak running Streakdroid 1.9.1, but just get Force Close every time.
Looks good, just ran a test tune for an NSX that I've just been using that was created using the spreadsheet and the settings data matched.
A couple of quick questions though, firstly, what is the alternative brake balance formula?
And second, I don't seem to be able to get my head around the export feature. I can only see the import/export option on the first screen and if I select it there it only lists your tunes that are built in to the app.
Ok and a sneaky third question, will Oppositelock's gear tuner be added in a future update?
Another thing I've just noticed, if you load a saved tune and want to compare it between version 1 and version 2 the data entered on the first page isn't saved so you have to add the spring rates, ride heights and poewr etc again. Is there any way this data could be saved along with the rest of the tune?
Does not work with:
Sprint - Samsung Moment - Android OS 1.5
*Don't ask me why, but this phone can't upgrade the android OS*
I'm puzzled by this: Could you pm with steps on what you are doing? I cannot figure out what you are doing.
Sorry, a case of operator error here, I hadn't saved the Car, I'd only saved the tune. All is working as you described now.
Cheers
Mark