Talk:Grouping and VisGrouping: Difference between revisions
No edit summary |
Angry Beaver (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
Anybody ever come across a problem with their visgroups seemingly locking up? I've a map that uses visgroups to a large degree, and for some reason I can no longer add or remove objects to existing groups. The visgroups still work as expected otherwise - I can still hide/unhide, combine, parent, etc... - it's just that I can't go into an object's properties and add or remove it from any visgroups groups anymore. I can also still create new visgroups using the "hide selected objects" tool, but I can't add or remove objects from those once they are made either. It's really annoying to have a map that uses a complex visgroup setup unable to have its visgroups edited, as now their purpose is pretty undermined by the fact I've a few hundred objects unable to be added to the groups they belong to. Is there a limit to the number of object/visgroup relationships you can have within a level or something? --[[User:ReNo|ReNo]] 07:46, 25 Apr 2007 (PDT) | Anybody ever come across a problem with their visgroups seemingly locking up? I've a map that uses visgroups to a large degree, and for some reason I can no longer add or remove objects to existing groups. The visgroups still work as expected otherwise - I can still hide/unhide, combine, parent, etc... - it's just that I can't go into an object's properties and add or remove it from any visgroups groups anymore. I can also still create new visgroups using the "hide selected objects" tool, but I can't add or remove objects from those once they are made either. It's really annoying to have a map that uses a complex visgroup setup unable to have its visgroups edited, as now their purpose is pretty undermined by the fact I've a few hundred objects unable to be added to the groups they belong to. Is there a limit to the number of object/visgroup relationships you can have within a level or something? --[[User:ReNo|ReNo]] 07:46, 25 Apr 2007 (PDT) | ||
:Theres none that I know of, take a look at the [[VMF_documentation]] it talks about how visgroups are stored in the vmf so you may be able to fix your problem manually. --[[User:Angry Beaver|Angry Beaver]] 13:44, 25 Apr 2007 (PDT) | |||
Revision as of 13:44, 25 April 2007
Anybody ever come across a problem with their visgroups seemingly locking up? I've a map that uses visgroups to a large degree, and for some reason I can no longer add or remove objects to existing groups. The visgroups still work as expected otherwise - I can still hide/unhide, combine, parent, etc... - it's just that I can't go into an object's properties and add or remove it from any visgroups groups anymore. I can also still create new visgroups using the "hide selected objects" tool, but I can't add or remove objects from those once they are made either. It's really annoying to have a map that uses a complex visgroup setup unable to have its visgroups edited, as now their purpose is pretty undermined by the fact I've a few hundred objects unable to be added to the groups they belong to. Is there a limit to the number of object/visgroup relationships you can have within a level or something? --ReNo 07:46, 25 Apr 2007 (PDT)
- Theres none that I know of, take a look at the VMF_documentation it talks about how visgroups are stored in the vmf so you may be able to fix your problem manually. --Angry Beaver 13:44, 25 Apr 2007 (PDT)