2022-05-11 06:04 AM - last edited on 2023-05-20 12:40 AM by Gordana Radonic
Hi all,
I have come back to an old project in which we used negative stories to build Modules. For some reason, when I go to export one of the modules, it includes every story up to zero... The other modules do not appear to be doing this...
I have changed the story structure for this module, but I do not see how that might be related. The relevant objects were all built by magic wand-ing the existing things and modifying their paths and positions so I do not think I have a rogue object... I have yet to find one...
Ling.
AC22-23 AUS 7000 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win10 | R5 2600 | 16GB | GTX1660 |
2022-05-11 06:27 AM - edited 2022-05-11 06:28 AM
Maybe you should select first the modules before exporting.
2022-05-11 06:48 AM
When you check everything except the two short railings...
AC22-23 AUS 7000 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win10 | R5 2600 | 16GB | GTX1660 |
2022-05-11 09:57 AM
Whelp. Now my module is being offset 25 stories up... >,>
AC22-23 AUS 7000 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win10 | R5 2600 | 16GB | GTX1660 |
2022-05-11 10:55 AM
@Lingwisyer I am guessing you have checked the publishing / save storey range setting for the rogue module? Could it be the module was saved with all stories below zero? That might explain the 25 storey jump.
2022-05-11 11:23 AM
are you linking the saved modules to a new file? if yes have you tried this settings?
2022-05-12 03:32 AM
Well... after a few weird exports yesterday, it works properly this morning...
I am selecting the module in 3D, isolating selection, then saving selection as module. I would get if extra stories were included, but the fact the the entire story structure was shifted messed up all of the stored story heights. Anyway, hopefully that was a one off event.
AC22-23 AUS 7000 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win10 | R5 2600 | 16GB | GTX1660 |
2022-05-13 04:38 AM
Not a one off... Zzz...
AC22-23 AUS 7000 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win10 | R5 2600 | 16GB | GTX1660 |
2022-05-13 05:29 AM - edited 2022-05-13 06:22 AM
Ah. It would appear that when saving a Module from the 3D window, the Homestory becomes which ever Plan Story you were in last. Good to know. Hopefully I will remember that...
I have also realised that using negative stories for modules is not very suitable if they are multistorey unless you leave extra placeholder storeys to accommodate any story structure changes. Story, storey, stories, storeys, storied, storeyed...
AC22-23 AUS 7000 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win10 | R5 2600 | 16GB | GTX1660 |
2022-05-17 11:26 AM
Usually need to clean up the stories if you plan to use it later on as a hotlink module. You should only retain No. 0 & 1 (from storey settings)