|
Re: FRC Simulators (That still work)
Quote:
Originally Posted by gblake
...
If I could remember how to activate the slick debugging features Dave Stevens put into the code (6-8 years ago)(using Lua and some other tricks), we could test my guess by seeing if we could get wireframe outlines of the physics models to appear. I sent Dave an email today, asking if he can dredge up any memories. Maybe his supply of memberries is fresher than mine.
...
|
Dave replied and told me that he couldn't get the old code to work either.
His guesses at the root causes were similar to mine. Software tends to corrode/erode over time in the sense that as libraries, APIs, device-drivers, etc. evolve, both their interfaces and implementations change, and ... if only one bit in one part of the entire system becomes incompatible with the rest ... the result can turn into driving a label around on a blue screen.
Sorry, but for now we may have to relegate the Fifth Gear simulators to the bone yard. Maybe some day someone will be able to pull a copy of the source code out of the repository we were using, and revive them for a nostalgia-fest.
Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|