If I input vtec to engage at 5200 and it actually engages at 5400 and switches maps at a different point from when the vtec solenoid gets 12v from the ecu, I would call that a bad rom editor. (P72 Code)
Who uses P72 code? Everyone knows CROME had 99% of its support with the P30 code. Using anything else and expecting it to work is dumb and then calling the software trash because of it is retarded.
The mantra of the Crome forum on pgmfi.org is "203 is the development ROM," has been for a very long time now. I haven't used Crome in 3+ years now, and that was the lay of the land then. With code being interchangeable, I see no reason why that would have changed.
Furthermore, if I disable something or add a plugin that renders the current file useless, I would call that a bad rom editor.
Never had this issue.
I've had it happen to me with Crome, Uberdata, once with eCtune. Never used Neptune but I'm sure I could get it to glitch on a long enough timeframe.
Non of these are due to incompetence, but actually due to the program's inability to function properly.
Blake had idle issues, that was incompetence. I've gotten ALL cars I've tuned to idle perfectly.
While this thread is titularly about Crome and it's shortcomings, the underlying current that Mr. Kerr seems unaware of is that the Junior Fumbler Crew is being taken to task.
even AEM and S300 have their quirks. I wouldn't call either of those softwares trash because they both do a good job of running an engine safely and effectively.
S300 is little better than Crome, Hondata has just polished over the obvious bugs and bought enough magazine adverts that sheep do not question. AEM, however, has fundimental issues NOT arising from the GEMS designed motherboard that is a form of awesome for a ten year old design, but from their complete inability to make 90% of the adapter boards that interface the GEMS standalone with whatever car you're plugging it into. Most of their electronics are borrowed designs, trash, or a mixture of the two.