Could somebody please post an explination as to what each variable that debugview outputs represents? I remember doom9 once did this for Nandub a while ago explaining what each set of numbers represented.
--------------------- 2002 IS 300 2005 X5 2008 335i
What does a line like this mean: [3020] P-frame quantizer prevented from rising too steeply And could you explain the overflow a bit more, I'm still sorta confused about it.
And these too please: [3020] avg scaled framesize:3565 I assume that is self-explanitory, but is that just the scale, or after the quantizer used also? [3020] bias bonus:499 bytes bias bonus is adding 499 bytes per frame? [3020] quant:2 threshold at 331 : -90 percent what is the threshold representing? and what is the percentage representing and why is it a negative value?
--------------------- 97 M3/4 ...420rwhp...Dinan SC Tuned by AA, M50 Manifold, RMS Aftercooler 3.5 Porsche HFM, 42# injectors, Supersprint Exhaust AA Turbo Clutch, AA LTW Flywheel, TCK Suspension AA Strut bars (F&R), XBrace, BMP Rear Camber Correcting Arm BBS RK wheels on
Could somebody please post an explination as to what each variable that debugview outputs represents? I remember doom9 once did this for Nandub a while ago explaining what each set of numbers represented. I know you were interested in the thresholding output from the PM (not sure what else there is) - can't tell you unfortunately because I can neither use xvid.dll nor browse the source on this computer (doh). Perhaps in a couple weeks when my travelling slows down. -h
--------------------- 95 M3 - SOLD 02 540i/6 - SOLD '12 Audi A6
Поиск
Users
Entrance
RE: Interpreting the debugview output
