10-02-2016, 06:02 PM
(10-02-2016, 05:45 PM)wolverine_i_am Wrote:(10-02-2016, 03:12 PM)Shannon Wrote:(10-02-2016, 02:12 PM)wolverine_i_am Wrote:Quote:Feeling a lot better. I'm back to working, although I get exhausted relatively easily, so I have to take a lot of breaks. But, I have been well enough to work today on the 6G prototype (Beast 9) and I discovered two things.
One is, Beast 8 has a HUGE error in the script that effectively strips out nearly all of the work I put into the script from Beast 7. This tells me I was not awake enough when I built it, so Beast 9 has to be built sooner than usual to correct this.
The second is, I have discovered some things that are really exciting for motivating people to do stuff! This has me really excited, because it's consistently showing well in the models and it;s really making a difference. If it performs well in Beast 9, it will probably end up in DMSI.
Not sure when I will have the time or energy to build Beast 9 though.
Does this mean you'll be prioritising the work on 3.0.x lately?
I'm curious about what the error is too.
Not necessarily, I have quite a bit of testing on this to do before I worry about putting it in DMSI.
The error is both simple and complex, and I will attempt to explain it without giving too much of how things work in the 6G prototype away.
It is simple because it was simply the fact that the last statement in a series did not get tagged. Without a tag, it isn't included in the voice script weaveout.
It's complex, because even if it had been tagged, a typo in the statement would have bypassed the entire statement's impact anyway.
Without that statement, almost all of the two months of work that went into Beast 8 were either bypassed or not included during build.
So how does this affect the results of 2.4?
I'm pretty sure it doesn't affect it.