Thanks again for the images.
I am not an experienced user of blender, just tested playing around importing Obj, texture mapping, simlle rendering .
Any video tutorial you remember ... or any feature / workflow you think worth implementing... ?
Thanks again for the images.
Not sure about implementing, but i always find it interesting to research other people's take on the same challenges. With Architectural objects, there seem to be plenty.
Nice, so this is a further level: let me repeat to check if I understand you.paullee wrote: ping
Just realize, after busy for almost a year, the test codes have not been further discussed here https://forum.freecadweb.org/viewtopic. ... 40#p317816[/b]paullee wrote: ↑Tue Apr 28, 2020 1:40 pm There are a few discussion so may be I just outline my own thinking.
Currently, Arch Object give you the solid geometry with some parameters which make up the BIM objects, Wall, Window, Stairs.
This is somehow hard for customisation of the form or the code will be more and more complicated (@Yorik explain this problem found in Revit). Stairs apparently is one which is complex in forms, so how do you model a stairs not Stairs, a curve auditorium etc.?
So, e.g. in this post [EDIT] https://forum.freecadweb.org/viewtopic. ... 40#p317816 , an option is added so Stair just return the Face or even Profile of the Steps, then one could Revolve to get a shape required. Even better if a Step Profile (e.g. in Sketch) is return, one can based on this step profile add details, then extrude into solid.
Instead of make a Gui tool just to generate a Stair Profile, Face etc, I am adding option to let Stairs to return a Profile, Faces, Solid object etc. This complicate the Stairs object in fact. I am not sure if a separate tool sharing similar code but just return the outline / profile is better solution - so a simple Stairs Profile / Geometry Object, then subClassing it to make the Arch Stair objects? Difficult for me to express due to my very limited knowledge in programming and python
Code: Select all
def setProperties(self,obj):
...
if not "StructuresOutput" in pl:
obj.addProperty("App::PropertyEnumeration","StructuresOutput","Structure","Profile, Face, Solid (Bim Object) or None to be created for Structures")
obj.StructuresOutput = ["None","Profile","Face","Solid"]
if not "StepsOutput" in pl:
obj.addProperty("App::PropertyEnumeration","StepsOutput","Structure","Profile, Face, Solid (Bim Object) or None to be created for Steps")
obj.StepsOutput = ["None","Profile","Face","Solid"]
Code: Select all
def execute(self,obj):
"constructs the shape of the stairs"
...
self.steps = []
self.risers = []
self.pseudosteps = []
self.structures = []
## TODO - 2019.5.20
self.structuresProfiles = []
self.stepsProfiles = []
self.risersProfiles = []
I am, of course, constantly comparing with the BIM software I use for work. With Revit stairs, different nosing profiles can be used, the nosing can wrap around the front and sides of the tread, the riser can be sloped. The tread and riser can be different materials. Customized railings with fancy balusters can be used, so many balusters per step can be specified etc etc. This may give you some ideas of what you would like to do with Arch stairs but on the other hand, you may say "the hell with that!"If you have any idea on Arch Stairs, you may comment here
Using a wire as a base reminds me of one of the Revit methods - stair by component. The user sets the top and bottom level parameters, along with the maximum riser height at minimum tread depth then dynamically sketches the path for each flight. I actually prefer the Arch stairs method because the base wire is placed before the stairs are created and can be tweaked to adjust the stairs afterwards. In Revit, I would have to go back and manually adjust each flight while playing with the step and level parameters, and it can be quite fiddly to do so.There have been a few area needs to be improved, like the base for which to build the Stairs which is not very handy currently.