Hi Christian.Both David and I have found visual artifacts ( severe image trailing ) occuring when:In Spot plane slew mode, and very near a placed library object that has a crash octtree code in the library BGL. Rotating the plane really shows it. Rotating a plane in slew on top of a building ( like on a helipad ) also shows it.If a library object is placed, that doesn't have the octtreee in the library code, then it's fine... even if the placement code contains the crash octtree ( like MakeMDL delivers BGLC code ).Weird, but maybe there is something in fsregen's library headercode, or somewhere, that messes up the display.. or maybe in the MakeMDL object code. I've read an extra return can cause this kind of havoc with objects.====================David's other problem, is that he doesn't like his default crashcode for his hedges. He wants a crash, but offset from the hedge, so a wingscrape doesn't crash the plane. A bonafide smash into the hedge should cause a crash.Looking at the BGLC code from MakeMDL, it does appear an offset could be made there:model_crash label BGLCODE BGL_CRASH_START model_crash_end, 142 BGL_CRASH_OCTTREE crash_end_1 dw CRASH_FLAG_OBJECT ; crash type dw 1 ; nodes used real4 -100.000000,0.000000,-100.000000 ; Box x,y,z real4 200.000198,200.000198,200.000198 ; Box w,h,d dw 1, 1, 1, 1, 1, 1, 1, 1 ; base offset into node table, one for each top-level branch ; So if you take branch 2 (count from 0), you add 1 to indices you encounter on that branch ; Nodes (254=empty 255=full, else an index into branch) OCTTREE_NODE 255, 255, 255, 255, 255, 255, 255, 255 ; node 0crash_end_1 label wordmodel_crash_end label wordThis is for a 100 meter cube, drawn at 0.50 scale 2.0 modeling units ).The "Box x,y,z" code placed in from the edges 100 units ( centered ) and at 0 height ( so it sits on the ground ).The "Box w,h,d" code controls it's size in modeling units.So the crash "Box" can be repositioned and shrunk, by alteriing values in that code.------------I also note the crash type might be changed.. and maybe that would also give him that effect:CRASH_FLAG_NONE equ 00 CRASH_FLAG_MOUNTAIN equ 02 CRASH_FLAG_GENERAL equ 04 CRASH_FLAG_BUILDING_EYE equ 06 CRASH_FLAG_SPLASH equ 08CRASH_FLAG_GEAR_UP equ 10CRASH_FLAG_OVERSTRESS equ 12CRASH_FLAG_BUILDING_PLANE equ 14 CRASH_FLAG_AIRCRAFT equ 16CRASH_FLAG_FUEL_TRUCK equ 18CRASH_FLAG_OBJECT equ 20The above cube uses "OBJECT" type... I was wondering if another type might work for his hedges.Otherwise he could place an object w/o crash code, then also place a CrashBox code, offset, or smaller than, the object.Dick

Hi Dick,Possible that fsregen stuffs things up. I hand code my stuff (don't have any examples here though which I could post). Then again I haven't tested my code in spot view (never use it)...Why use an octtree at all for hedges? A simple box would do (ie use old crash commands).I usually change the code to CRASH_FLAG_BUILDING_PLANE, which is usually the one to use (it means crash between a plane and a building which is correct in most cases). I think CRASH_FLAG_OBJECT is a sort of general flag, if you don't know what else to use... I don't know if this really makes any difference though...Cheers, Christian