what is that supposed to be? user settings export?
viewport mode ini → import it in the view → display modes → import
Then it’s a setting and can be configured 
I want to exploit it what is it how is it setup.
Dude WTH did you do, it’s 2:30 and I can’t go to sleep because I have to figure it out 
Thanks Gijs. I’ll look forward to checking it out. And see if it only works on closed polysurfaces. Section Tools works even if they aren’t closed.
It’s must be a combo - he did something with the clipped objects and the display mode. Just the display mode doesn’t work in my template. XD
I was about to ask you 
Nope
assign a material (texture) to that clipping plane and it should work (or simply copy over the clipping plane from the file I posted to see its settings)
1 Like
Are you sure this is correct?
well, I mean no bitmaps
There’s the catch, so you lied
same thing bitmap = texture 
you almost got me
guilty as charged
2 Likes
So, I played with materials to emulate clip hatches. It’s not easy/simple or straightforward. It’s also a huge performance killer. The more objects clipping plane cuts through, the lower frame rate you get. It’s not gonna be viable for medium to large architectural models. You’re going to hate life even setting up your views in your details.
1 Like
Alan’s post up near the top about Section Tools is what I would now echo.
I’ve gone back to it. I find Section Tools awkward, but it’s the only efficient reliable way to create fills, and as far as I can tell it’s the only way to do it on some open polysurfaces.
But I’m only using it to create the fills, and using clipping planes* for clipping sections. That’s because though the st fills appear in the model in any view, the st section can only be set to clip in one view (as far as I can tell) which means clipping planes are required for every other view. This means creating a clipping plane plus a Section Tool section for every section view (except one).
It’s cumbersome, but it’s the only reliable way to create section fills, as far as i can tell.
*that’s for 3d view viewports. For 2D views I’m using VisualArq Section/Plan Views (not make2D) because they’re updatable. To align 2d views with st fills I move the 2d views to where I’ve put “stLayouts” (the name st gives for stfills placed independently from the model in the project). I don’t move these stLayouts to the 2dviews – 2 reasons for this 1) stLayouts can’t be placed with precision when they’re generated and 2) they can never be moved (stMoveSection only moves the plane where the section intersects the model.)
Maybe this points to a resolution.
Mayeb a one word command trigger this script in this post: Surface to hatch (inverse of explode hatch)
Maybe spend a couple of hours to understand and combine the two scripts. Create custom toolbar and button and make the button run the script? 
That doesn’t sound like much work for a developer or someone who codes but it seems like a lot more than two hours’ work for someone who knows nothing of coding (like me, for example.)