2 weeks ago
Operating system used: Windows 11
2 weeks ago
A window will only cut a hole in the one wall it is associated to (placed in).
Adjacent walls will not be cut by the window.
So in this case, you can extend the lower portion of the wall along to the corner and stack the second wall on top.
Or you need to place an empty opening in the tall corner wall that matches your window opening.
Barry.
a week ago
@JaredBanksrecently posted a tip about how to create those openings in the other Walls:
https://community.graphisoft.com/t5/Modeling/Create-Opening-from-Selection/m-p/700300#M179316
Tuesday
See this wish: https://community.graphisoft.com/t5/Wishlist/Opening-Tool-as-Standard-Wall-Penetration-Tool/idi-p/26...
| AC22-29 AUS 3200 | Help Those Help You - Add a Signature |
| Self-taught, bend it till it breaks | Creating a Thread |
| Win11 | i9 10850K | 64GB | RX6600 | Win11 | R5 2600 | 16GB | GTX1660 |
Tuesday - last edited Tuesday
It's interesting to observe that that wish was posted 5 years ago in 2021, and at some point made it into the roadmap (not really sure when, exactly) but here we are 5 years later and still no implementation onto the program itself.
It's also impressive that it was able to get onto the roadmap with (as of typing this post) 54 votes - especially when you consider that you can have wishes with as many as 180 or upwards of 200 votes getting placed "On Hold". And I'm not trying to diminish this wish request or suggest it shouldn't be given importance, but it's just fascinating to me how Graphisoft chooses to prioritize wish requests, or to execute things related to the program development.
The less said about other things that end up on the Roadmap (or even eventually onto the program itself) that never once made an appearance on the Wishlist section, the better for everyone.
Tuesday
More strange is that the wish seems to no longer be in the roadmap, even it´s still marked as such 😮
Tuesday - last edited Tuesday
@Jp1138 wrote:
More strange is that the wish seems to no longer be in the roadmap, even it´s still marked as such 😮
I suppose we've reached the segment of the schedule where even wish requests are getting shadow-banned.
Is there even any connection between the Wishlist section and the Roadmap any more?
It's sad to see people soliciting support for the wish requests they've made and trying to get other people to vote for them, in the hopes that it will amplify them enough for GS to consider even researching implementing them, - only to realize you're not even on their radar, any more than they ever have (or had) any plans or expecations of even considering your wish (if they even know about it, at all).
What even is the point to any of this, then?
Thursday
The expansion of the Opening Tool functionality that came in AC29 is apparently seen as a move towards this wish...
@Bricklyne Clarence, quite a few of the On Hold wishes that I have noticed are ones that require reworking of old tools, or have similarly been marked as require a lot of work to accomplish... Even if we did not see an improvements for a few versions in relation to them, it would be nice if they were on the Roadmap and slowly ticking away in the background. Instead, they are put "on hold" and shelved away even after been marked as important...
Ling.
| AC22-29 AUS 3200 | Help Those Help You - Add a Signature |
| Self-taught, bend it till it breaks | Creating a Thread |
| Win11 | i9 10850K | 64GB | RX6600 | Win11 | R5 2600 | 16GB | GTX1660 |
Thursday
@Lingwisyer wrote:
The expansion of the Opening Tool functionality that came in AC29 is apparently seen as a move towards this wish...
@Bricklyne Clarence, quite a few of the On Hold wishes that I have noticed are ones that require reworking of old tools, or have similarly been marked as require a lot of work to accomplish... Even if we did not see an improvements for a few versions in relation to them, it would be nice if they were on the Roadmap and slowly ticking away in the background. Instead, they are put "on hold" and shelved away even after been marked as important...
Ling.
I've heard this explanation before, and without necessarily being dismissive of it, it is a bit problematic in several ways.
(...even putting aside for a moment the fact that in some of them, GS folks themselves said that the reason they were put on hold was definitively NOT because they were too hard to accomplish or to do).
The problem with it is that some of those wishes being put on hold for the reason you stated are wishes that have existed in the Wishlist section (firstly, in the old section, and then migrated over to the revamped one when they were upvoted as most popularly requested wishes by majority of users), for the better part of the last 10-15 years or more.
They can't possibly be finding out only now that these are complicated changes or fixes to enact?
Because that would imply they've been ignoring the Wishlist section for the better part of this century, even while giving poor unsuspecting users the misguided impression that their efforts to suggest wishes were not wasted or pointless gestures.
So giving them the benefit of a doubt, and instead taking the position that they've known about them for this long, the implication is therefore that upon discovering that some of these things are too complicated to do on the current (legacy?) code, they never developed a plan in the background to deal with them, or perhaps to start a revamp of the program code that could potentially have seen a new version of Archicad in about 15 or so years (or a few years from now) that could handle the changes necessary to enact those wish requests.
Some of the things being requested are standard features now, not just in current design programs, but in programs writ large across the board.
How is it possible that their rivals and peers could have foreseen the necessity for their programs to handle some of these functions and worked towards making them available for their users, but Graphisoft somehow missed the boat or just plainly lacked a plan?
To me that's just irresponsible, if that's the case of what happened here.
Because in the meantime, we've seen them spend resources on questionable features that were never requested and on others that were left on the wayside once users didn't take to them, or worse yet, on others that seem to exist only for the purpose of helping them sell more licenses and to market the program more than to help people work better - all while the things that people are requesting to be improved seemingly either get ignored or put on the backburner.
Because of this irresponsible strategy and decision making (...In my humble opinion),.... by the time they do get around to fixing some of these issues, some of us will literally be retiring from the profession.
I'm not even being hyperbolic or exaggerrating.
I wish I were.
Try to think of that in terms of the trust, faith and loyalty that some have invested in them over the years and how all that now gets repaid.
Thursday
Going very off topic for this thread...
I feel like it is a bit of all of the above, as there have been wishes for simple things which should only take a few hours to accomplish for a relevant developer in the know that would improve quality of life and reduce workarounds, and other wishes that while obviously difficult would be a significant improvement for the general userbase and should be on a longterm road map somewhere instead of being put "on hold" or even disappearing completely. The roadmap as it is is like faux transparency, there are no timeframes and things appear and disappear from it without any notice. Wishlist status also appears to be independant of the roadmap...
Ling.
| AC22-29 AUS 3200 | Help Those Help You - Add a Signature |
| Self-taught, bend it till it breaks | Creating a Thread |
| Win11 | i9 10850K | 64GB | RX6600 | Win11 | R5 2600 | 16GB | GTX1660 |