Obviouslybut the biggest miss, The decision was made before a new LTS version (v2.93) released and a new massive update (v3.0) , maybe now at version 3.0 after a huge overhaul in blender, Will be a good stopping point.
dropping the win7 support makes it possible to implement more win7+ features and removes a system to take care off and solve bugs. I understand that you dont like win 10/11 and dont want to update, but Operating systems are dead after some time and win7 is dead for 2 years now. MacOS ist supported from 10.13 and up, thats from 2017 so no difference there. You cant support an OS forever. How long do you plan to use win7? You have to update windows or switch to a different os anyway.
May i please have references as to what caused the decision regarding python and what prompt the change to a newer version? (As in, do you have discussions / back and forward with other developers about the issues that prompt the usage of a newer version?)
Immediately after the change of Python version, and the new requirement for a new Windows, it was indeed possible to do simple hacks to get it to work. But almost every day since it has diverged more and more. We are able to simplify code by not having to allow compiling for Win7. So for example there were many Windows API functions that we could now link to statically, rather than load dynamically. The changes now are very large and I would not recommend anyone taking their time to attempt it.
Making Blender usage easy to start is something I always try to look at. In my personal opinion the easiest and nicest way is always to unzip any software distribution and run it from that fresh directory.
Without having to do anything.
Another reason to use these defaults with the user level permissions is that with admin level it was often possible to install Blender in such a way that writing configuration files (startup.blend) or installing addons was impossible, due to wrong permissions for the (normal) user. We want our users to be able to do both things, naturally.
@Ben Lau, I have the directory with the installer definition scripts checked out (plus the rest of Blender for Windows; I often build it from source to get the latest fixes). Where in the build process would I find the NSIS step? Thanks!
When you specify the nsis target the file 00.sconsblender.nsi is used to create the actual script. Anyone who is interested in working out a better installer can look at the mentioned template and the function def NSIS_Installer in btools.py. The mentioned function creates all the necessary file lists, puts them in the installer script template and finally runs makensis.exe.
for me zip only is the better solution too!The biggest benefit is that we can have a vesion on flash usb and this makes easier to start your current version from any computer! plus, now, as Blender is not in final version yet many of us are using more than one version! and installer will broke any previous versions! for instance i am using very old version (4-5 months old) for modelling, because there is an addon for toggling edge-face -vertex mode with spacebar and this particular addon dont have a version for the newer builds! i think that there are many users like me that use some old versions from graphicall for their particular reasons!
In all honesty, I have never had any issues with the current installer and surely the people who are having issue with the installer are in the vast minority of total installer users?
As such, modifying the install path will add extra work to the users who dont have issues with the current installer.
I would be glad to create an installer of Blender for you to check out. I have considerable experience with it, and have done much Pascal scripting to create advanced installers. Let me know at haymondsoftware AT gmail DOT com.
I too think, this is a bad idea. Loading it into the profile data will not work very well in corporate environments, as the profile is completely send to the clients during login. Also, as an administrator, I *want* the user to be unable to update blender.
Also, I would like to have an MSI-package for pushing updates to my clients within LANdesk or similar suites. We have six PC studios with 30 computers each and we are trying to not have to update the images for the PCs all the time. Pushing new packages through LANdesk is much more convenient
No start menu item will be created and no blend-file association will be registered,but there is also no need for administrator rights. You can register the file associationmanually by clicking Make Default on the System tab of thePreferences. Alternatively, you can run blender -rfrom the Command Line.
When an update for Blender is released, it can be downloaded directlyfrom the Blender website.The Windows installer can then be run to install the updated version of Blender.To remove a previously installed version of Blender,use Windows settings or control panel to uninstall the desired version.
When an update for Blender is released, it can be downloaded directlyfrom the Blender websiteand extracted to the desired folder, where you can double-click the executable to run Blender.For more information on creating a portable version of Blender, see the section Install from Zip.
Hi! I am new to Blender BIM and BIM in general, which I am trying to learn with the BB add-on. So I am sorry if my question is going to sound very simple maybe, but I could not find a straightforward answer online (tried all day long).
The main problem I am having is with curved objects. I managed to create a custom window with a upper arch, but when I use it, of course, it creates a rectangular opening on the wall. Then I have tried using opening elements (modeling the shape of the window and then add void), to create voids where I could put my custom window, but I am definitely missing something because eventually I couldn't get it to work. What would be the correct worflow for this? Is there anything I can read or watch on the topic?
I have a similar problem with portals and archway, but I am hoping to understand it eventually once I solved that (the project I am working on is about HBIM so a lot of arches and complicate geometry)
Blenderbim has a couple of tricks to help with this: if you model an opening for a window instance, blenderbim will find it and make a copy of it when you create the next window; or if you add a 2D 'Profile' representation to the window type (ie. draw the elevation of the hole), blenderbim will extrude it and use it to cut openings for new window instances.
@brunopostle said:
Blenderbim has a couple of tricks to help with this: if you model an opening for a window instance, blenderbim will find it and make a copy of it when you create the next window; or if you add a 2D 'Profile' representation to the window type (ie. draw the elevation of the hole), blenderbim will extrude it and use it to cut openings for new window instances.
I have tried adding an elevation profile to the type, but it doesn't work.
As for the first method, that's why I was asking for the right workflow: I probably make a mistake at some point while adding the opening but I can't figure it out, and I haven't been able to find a tutorial about this.
I am attaching a simple example file.
This is also the same workflow I used before, now I have tried to update Blender and it works! Thank you so much, I wouldnt have thought about updating the software if it wasn't for your comment, knowing what I was doing was correct was very helpful. And it works with the instances too
There are two types of openings: semantic and unsemantic. Unsemantic openings are merely booleans used to create a shape (i.e. a modeling technique). For example, you could model a sloped wall by having a boolean applied to it. This is not meaningful for construction, it's just "the shape that the object has". These are simply represented using "IfcBooleanResult" as part of the modeling process.
Semantic openings have meaning and purpose in construction. The most common type of semantic opening is an "IfcOpeningElement", which represents a penetration in an object (most commonly slabs and windows) which have implications for fire and acoustic requirements, services coordination, or placement of other elements (e.g. a door is placed to fill an opening) and so on.
Another semantic opening is a "VoidingFeature", which represents material being subtracted during manufacturing and fabrication, and can store information about how the item in manufactured, including whether it is milled, drilled, etc.
Thank you! This is clearer. I figured out the voids and windows openings. Regarding the arch itself, which in my case is more like a portal than a door, what I have done so far is creating a IfcElementAssembly that contains both pillars and the slab which has the opening shaped like the intrados. It seems more semantically correct than creating an opening in a wall, but I hope I am not missing anything (VoidingFeature doesnt apply to this case I believe).
Hi which blender version and which blenderbim version works for this arch window workflow. I've tried blenderbim stable 040323 and blender 3.4 and I don't get a rectangular opening, green wire frame or anything. I don't get any opening when window is added, add void produces some kind of weird blue cube which doesn't create opening to match window. cheers Newbie99
@fired66 said:
Hi which blender version and which blenderbim version works for this arch window workflow. I've tried blenderbim stable 040323 and blender 3.4 and I don't get a rectangular opening, green wire frame or anything. I don't get any opening when window is added, add void produces some kind of weird blue cube which doesn't create opening to match window. cheers Newbie99
Hi, sorry I am late. In Blender 3.4 and BlenderBIM 230328 (but I tested it with older versions too) everything works.
My suggestion is firstly to try to understand openings using a sample library like this one below.
Add a wall - select it - move you 3D cursor on the surface of the wall - add a window - select the wall again - click on the "eye" icon in the "Active Tool" panel - you should see the rectangular opening in blue.
3a8082e126