|
| 05 Nov 2013 05:08 PM |
| I would love to use SelectionBox, but unfortunately, they cause to much lag, especially for my use, anyone know any other alternative? I was thinking about using a brick instead to make the outlines, but I don't think it'll make much of a difference, plus it'll a huge time consumer. |
|
|
| Report Abuse |
|
|
|
| 05 Nov 2013 05:08 PM |
| *it'll be a huge time consumer. |
|
|
| Report Abuse |
|
|
rrytry
|
  |
| Joined: 21 Aug 2012 |
| Total Posts: 4151 |
|
| |
|
|
| 05 Nov 2013 05:16 PM |
| It's not lagging a lot, it's just noticeable, either that or I'm just imagining it lol. |
|
|
| Report Abuse |
|
|
adark
|
  |
| Joined: 13 Jan 2008 |
| Total Posts: 6412 |
|
|
| 05 Nov 2013 05:18 PM |
| You're probably just imagining it, or your script is making enough SelectionBox objects to start lagging your computer. |
|
|
| Report Abuse |
|
|
|
| 05 Nov 2013 05:21 PM |
| I wish there was a object like the selection box and old force field mixed together, that would highlight the model not a part (I know with the selection box you can make it over a mdoel, but it'll make a normal square box) |
|
|
| Report Abuse |
|
|
| |
|
adark
|
  |
| Joined: 13 Jan 2008 |
| Total Posts: 6412 |
|
|
| 05 Nov 2013 05:26 PM |
| You can implement that really easily by just putting SelectionBoxes into every Part in the model... |
|
|
| Report Abuse |
|
|
|
| 05 Nov 2013 05:29 PM |
| Adark he meant outline the model itself, not the parts inside it, and not making a square around the model either. |
|
|
| Report Abuse |
|
|
adark
|
  |
| Joined: 13 Jan 2008 |
| Total Posts: 6412 |
|
|
| 05 Nov 2013 05:37 PM |
| Then make an invisible, non CanCollide part around the model and attach a SelectionBox to it. :/ |
|
|
| Report Abuse |
|
|
|
| 05 Nov 2013 05:39 PM |
@adark No, I mean like The old forcefield would outline every brick within the model its in (And models in models, and models in models in models) with only one force field object I wish there was a selection box like that. |
|
|
| Report Abuse |
|
|
cntkillme
|
  |
| Joined: 07 Apr 2008 |
| Total Posts: 44956 |
|
|
| 05 Nov 2013 06:18 PM |
^ recursion...
Anyway, SelxBoxes never lagged me |
|
|
| Report Abuse |
|
|
|
| 05 Nov 2013 06:19 PM |
@Cntkillme We know that it can be done with a lot of selectionboxes But the idea is to use only one object, like the old forcefield did |
|
|
| Report Abuse |
|
|
cntkillme
|
  |
| Joined: 07 Apr 2008 |
| Total Posts: 44956 |
|
|
| 05 Nov 2013 06:20 PM |
| Oh, though the old forcefield made multiple boxes anyway... |
|
|
| Report Abuse |
|
|
|
| 05 Nov 2013 06:23 PM |
That was the point of the idea A selection box that would make a outline around every part, using only one object. Like the old forcefield |
|
|
| Report Abuse |
|
|
cntkillme
|
  |
| Joined: 07 Apr 2008 |
| Total Posts: 44956 |
|
|
| 05 Nov 2013 06:24 PM |
| Then just put an intvalue named 'highlight' and in another script let it illiterate through everything and make the boxes for you |
|
|
| Report Abuse |
|
|
|
| 05 Nov 2013 06:28 PM |
| The point of it is to do it with one Selection object though >.> not just to highlight every brick |
|
|
| Report Abuse |
|
|
adark
|
  |
| Joined: 13 Jan 2008 |
| Total Posts: 6412 |
|
|
| 05 Nov 2013 09:16 PM |
You are missing the point. There is no reason to have a recursive box like that, when it's loads more useful to have a much simpler, non-recursive box that can be scripted to look identical tot eh recursive one while still remaining independent of that recursion.
There is not and never will be a reason for an object like that to exist. |
|
|
| Report Abuse |
|
|
|
| 05 Nov 2013 09:19 PM |
| Sorry, theres NO object to have a selectionbox on every part inside a model, it has to be recursed. |
|
|
| Report Abuse |
|
|
|
| 06 Nov 2013 08:44 AM |
We knkw there isn't one, but there used to be one. It was the old forcefield @Adark What if the model has a ton of parts? The loop would lag, plus all the new objects will lag |
|
|
| Report Abuse |
|
|
adark
|
  |
| Joined: 13 Jan 2008 |
| Total Posts: 6412 |
|
|
| 06 Nov 2013 12:52 PM |
An intelligent loop will never itself lag, especially if only run once.
As well, the new objects will not lag all that much, especially compared to a laggy script.
Besides, it would take thousands of parts to lag at all. |
|
|
| Report Abuse |
|
|
|
| 06 Nov 2013 01:26 PM |
| The old forcefield didn't lag when put over thousands of parts |
|
|
| Report Abuse |
|
|