27.03.2008, 11:06
You entirely miss the point.
Before, we'd get a plane in a new patch, and we test it, and we KNOW it's wrong, but what can we do, it's a black box. Right now, anyone can theoretically open up a new plane and read the FM data, but why should we have to? It should be OPEN for any that want to try and understand. Not the "black box" aspects, many of us simply don;t have the time. The DATA, though, would be useful.
Post the fmd file (plain text), for example.
Having the changes from a "stock" plane remarked will also help people working on new FMs in the future as well. It might be discovered that there is an interaction between something in a class file and the fmd data, like the fmd value is used if something is set to -1 somewhere, otherwise it is overridden by the value in the class, etc.
Having the FM stuff entirely a black box means that all that is learned about it is only known by 1 or 2 people, everyone else wanting to pitch in is either SOL, or they have to start from scratch and reinvent the wheel.
tater
Before, we'd get a plane in a new patch, and we test it, and we KNOW it's wrong, but what can we do, it's a black box. Right now, anyone can theoretically open up a new plane and read the FM data, but why should we have to? It should be OPEN for any that want to try and understand. Not the "black box" aspects, many of us simply don;t have the time. The DATA, though, would be useful.
Post the fmd file (plain text), for example.
Having the changes from a "stock" plane remarked will also help people working on new FMs in the future as well. It might be discovered that there is an interaction between something in a class file and the fmd data, like the fmd value is used if something is set to -1 somewhere, otherwise it is overridden by the value in the class, etc.
Having the FM stuff entirely a black box means that all that is learned about it is only known by 1 or 2 people, everyone else wanting to pitch in is either SOL, or they have to start from scratch and reinvent the wheel.
tater