That is disappointing.
That is disappointing.
Might want to contact HPT and tell them to fix their betaI could probably write a fix for it to convert it to the proper format but geeeeez that would be a PAIN IN THE ...
and I would remove it when they fix their simple glitch.
The disappointing part is not your software, was referring to HPT.
Ohh I know ... just making it clear for anyone joining the thread. I think this is the second time Ive run into this particular issue with HPT on two different versions. Must be a common mistake.
They don't care. Just like the really don't care about getting the newest version out. we are going on like 3 years waiting for V2.24 to come out.
They are more interested in selling their product that doesn't work correctly to new markets than helping the people that already bought it.
See thats where Im different ... Im supporting the hell out of my customers ... and they arent paying
^indeed props to you sir!
...i need a job now so i can donate again! haha
Caution:Slow Learner
Maybe HPT should just turn their source code over to me.
It's not just your software it effects. It's anything that I want to use the exported data for. The Engine speed comma has screwed up the whole file.
How about "Occupy HPTuners"?
Sounds like a plan ... do we have a plan for food though because without good food Im out.
Does anyone know if this has been fixed yet?
Last edited by NFJ; 03-06-2012 at 07:37 PM.
Have an issue? What issue are you talking about because there are hundreds using it right now? I know of a few issues that Im working on so youll have to be a little more specific.
i get TPS error message
HPTuners exporting the CSV file. They decided to add a comma in their engine RPM causing a shift in columns anytime one goes over 1000 RPM in their current BETA softwareOriginally Posted by bbarnhill
if that column had quotes around it that wouldnt matter in CSV ... but since its COMMA seperated values ... without quotes ... it matters. Such a simple fix.
When I brought it up to them before, they said it wasn't an easyfix. But i have no idea. either way between this, waiting for 2.24 and not being able to use stand alone datalogging correctly HPT is really dropping the ball.
Might be time to switch over to EFI live.
how is that not an easy fix unless they don't have any developers on staff? You would think such a simple fix ... and I'm a developer saying that. It cant be something hard to find unless it is atrocious code, which wouldn't surprise me from past experience looking at peoples code. Not that someone would call Virtual Dyno clean code, as when I started it I never intended it to go where it has gone. It was a proof of concept and it took off. If I had known it would have taken off like this I would have designed it a bit better but it works ok and Im cleaning up the code a little at a time with each release.
How long is their release cycle?
Never.
1994 Mazda Miata turbo, aero, hoosiers Class=SSM
Take my drop box referral and we both get an extra 250 Mb free!
lol who knows.. 2.22 was new 3 yrs ago? i heard somewhere on here that it was 6 months.. but it keeps getting pushed back.
Now I dont feel so bad being 2 months between releases. Im finishing up 1.1.8 right now working on the drag and drop issue people are having with UAC turned on. Im taking the elevation code out so it no longer requires administrator and taking some other things out that dont need to be in there anymore. Just sent beta 7 out the 'door' to betas tonight. If it gets positive feedback Ill release 1.1.8 and begin on 1.1.9
Reply With Quote