Mike Glover said:Hello Everyone,
My original plan was to have 1.30 up on the website on Jan 3rd, but I did not
work from the 23rd thru the 2nd, so the bugs that krept into the editing while
comparing/viewing two calibrations did not get fixed. I am still wrestling
with that and some copy & paste quirkiness.
Anyway, I will put it up on the website no later than Noon tomorrow, but as
1.30 Beta 3 though it is pretty close to production. I will post a long winded
breakdown of what has been done with it and what is next.
I have been trying to get some guys to verify/test some logging fixes, etc..
for me, but have not had much luck...trying commando style...so while it is in
"Beta" (here come the flames!!!) I need to get as much correction done on the
registers as possible. The 89-95 stuff is solid, 96-98 needs a couple of
corrections, but I don't have much on the 99 and up except for the 03-04
cobras.
Anyway, I will spell out what I need and where to send your bugs & correction
emails to. Also, we are adding support for about 500 additional strategies, so
lots of work ahead of us.
Best Regards,
Mike Glover
A Post Made By Cougar 5.0 said:Hey Everyone,
Well, I am cutting it closer than I had planned, but just under the wire!!
Always trying to get that "one last" item fixed.... I am still working on the
Whats New details and Whats Next. A quick list of primary features is below,
this is not a complete list.
PLEASE DO NOT EMAIL ME AT info@... WITH BUG FIXES OR FEATURE REQUESTS,
I will post email addresses for these later today.
This Update is just THAT, an update to 1.30A9 (A10 actually) and installs OVER
what you already have. BUT it MUST be a 1.3x release.
The update requires updating the USB & DATAQ driver & OCX. The install guide
will spell out the steps for updating the driver. The OCX is registerd
automatically. If you don't use a DATAQ, then it does not affect you.
I did have to disable editing while comparing calibrations, you can still
compare two calibrations but no changes can be made to the Functions or Table
data while comparing. This did not affect the Scalars Tab, at least not as far
as I have seen.
PLEASE make sure to read through the Getting Started PDF (Manual) before asking
questions regarding features.
Download the Install Guide (PDF) and follow the steps listed.
http://www.tweecer.com/dl/RT130B3IG.ZIP
Short List of new features, etc:
CalEdit
- Load & Compare a 2nd calibration, all functions, scalars & tables show both
calibrations
- Range selection functions for tables with right mouse click popup menu
- Standard Clipboard from CalEdit (buggy & can't go to CalEdit, yet!)
- Spin button increments & decrements values by minimum change allowed
- Whole host of fixes
CalCon
- Added all 4 channels for DATAQ devices
- Added support for 154 & 148, including USB (comm port select buggy)
Best Regards,
Mike Glover
So Grady, tell me how you REALLY feel!You do bring up a good point however, if what you are using works for you and you don't think you need any of the improvements or fixes in the software then definitely stick with what works... nothing wrong at all with that. That is just plain smart.
As a software developer myself I see both sides of the issue with past releases. After messing w/ the new beta, however, it looks like things are on the right track.
If anything, it is worth downloading for the new and improved "Getting Started" PDF.
The CBAZA definitions have been updated as well - lots more functions/scalars/tables available.
The ability to compare binaries/tunes is included.
DataQ USB support is there as well.
I'll keep everyone posted on my experience with the new versions... so far it's been positive.
Wes
Where do we get the A10 version. Tweecer.com still has A9 up.
when messing around with the new version earlier, I found the infamous
"Update Only" box was checked by default again.
This is the check box Grady mentioned above, which randomly corrupts your tune.
I don't know if the curruption problem has been fixed or not, but it does seem that the box tends to be checked by default.
Can someone else confirm this?
It is possible to download multiple versions of CalEdit on your machine.
For a while I was running both A9 and A10 on my laptop.
My understanding is that the "Update Only" checkbox flags only the portions of the binary file that have been changed and updates only those. I've never used it and have never had it toggle on for me. (A9 & A10)
I have both A10 and the newest beta installed in separate directories - no problems, both co-exist together well. I've even got a tricky setup where the datalog and CCF folders for both version are each mapped to the same directory that is located in "My Documents" so that I can get to it easier than trudging through Program Files every time - it's a symbolic link feature of NTFS for those familiar with *nix.
The instructions and also where to get the latest build are at: http://www.tweecer.com/dl/RT130B3IG.ZIP
One thing to note is that A10 is *NOT* the latest build.
Wes
Stanger007, I am surprised to hear you haven't had issues with the 'update only' box.
Maybe the bug is/was strategy based?
I have spoken to others who had the same issues, but I don't remember if they were GUFB or what?
I'm not sure why I never had problems - I've always used CBAZA and had no problems. A couple friends of mine that I've worked closely with on their twEECers also never had this problem. (both CBAZA as well)
Wes
My "Update Only" is at the bottom of CalEdit, version A9, A10 and B3.What exactly do you do/look at to make sure it does not update only?
I've never loaded v1.20 so perhaps that would explain my good luck. The OCX and twEECer drivers (read: how the computer talks to the twEECer) most likely were upgraded between the two versions as they were again for B3 - maybe something was not updated that should have been when going from v1.20 to a higher version?Maybe you can shed some light here
I'm not sure why I never had problems - I've always used CBAZA and had no problems. A couple friends of mine that I've worked closely with on their twEECers also never had this problem. (both CBAZA as well)
Wes
You guys that have never had a problem with the 'Update Only' checkbox...I have also never had a problem with this. Been using the Tweecer for a year.
Thanks Grady,
But the linky no worky...
You guys that have never had a problem with the 'Update Only' checkbox...
Are you in the habit of making minor changes to a tune, then loading it to the tweecer without saving the file first?
I think the problem only came up for me when I didn't save the tune before loading to the tweecer.
Any of you guys using TunerPro or Clint's BinEditor?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?