- Mar 6, 2014
- Reaction score
- Saratoga, CA
Yes you did. But what you didn't say is that GPS would later be required even for people running only Rx heads if they have a V4 CPU. That's changing something that didn't exist before.I have said it since the TX Sensors came out that GPS would be required and AntiLaser WILL NOT change this requirement. We have had this same conversation for over 2 years and they are not going to change this.
@angrypenguin just did, in this thread no less. @omgboost and I provided additional examples.We have 1000's of customers running this configuration and no one has an issue with this except a handful of members here that don't like the GPS requirement Show me this being an issue in the real world. .
The arrogance of those at AL HQ just shows how badly they need competition. They can't even get all of the damned bugs out of their software and they are continuing to add features and causing regressions. And they clearly don't test their code thoroughly before shipping it because they've shipped stuff with some pretty bad bugs. Errors EVERY SINGLE TIME they're started in a vehicle with laser FCM and there's any sort of object within 15 feet? Come on. As customers, we pay them to add support for the latest guns and fix all of the bugs. We shouldn't have to spoon-feed them bug reports for stuff as simple as that. I can understand if it was some really obscure test case that's only encountered very rarely, but this is very simple stuff. Maybe it's about time they actually start fixing issues instead of trying to add more crap on top of their broken code base. Only reason they continue to go down this path is that they're currently on top and they don't see it affecting sales.HW2 CPU's were never sold requiring the GPS so they cant force that requirement on older systems already sold without the requirement... GPS requirement was added with the TX Sensors and all new HW versions will require it as standard regardless of the configuration. Love it or hate it that is their policy and no whining or complaining is going to change it.
Here are the bugs I've encountered just in the last three days:
1. Pulling out of garage, the ALP beeped 6 times as usual, but didn't announce "interference defense active". This has been intermittent and occurs seemingly randomly since I installed the old equipment in my new car.
2. After upgrading the firmware, I had to reset & memorize sensors again, which is a known issue. I decided to pull a stats file, to make sure the new configuration was the same as the old configuration. I accidentally tried to "Save to USB" without a USB device inserted. Of course, writing failed. I then plugged in a USB device and writing still failed. I tried again and writing failed again. I then rebooted the device, and writing succeeded. I've tried to reproduce this but it appears that this is another bug that occurs intermittently or randomly. And I didn't have time to test whether this bad state actually affected the ALP's ability to jam, but given what I've seen on this system, I don't trust it to do what it's supposed to when ANYTHING unusual happens. I am trying to reproduce this bad state again to see if jamming is affected but I've been unsuccessful.