About Us

timd · 19-01-2005, 03:36 PM

An object that I'm modelling has opened up today as read-only -- I can't do anything to it! Have i tripped a switch somewhere? In the Finder, Get Info shows the .lwo file to be unlocked...

TIA,

Tim

Mark · 19-01-2005, 06:19 PM

Hmm... What version of LW? I think this is a known bug in 8.0. There's a number of ways you can work around it.

The first is to simply copy the entire object, layer by layer into another one and save... tedious, and you might miss something such as maps, etc... but works.

Another option to try is to run modeller without the hub (don't know how to do this on the Mac - on a PC add the switch '-0' (that's zero) to the command line)

Hope this helps...

timd · 19-01-2005, 06:24 PM

Thanks, Mark --

I'm using 7.5 (8.0 arriving this week). Will give the cut-and-paste a try.

Petrograde · 27-01-2005, 10:24 PM

I've had this happen a few times. I'm still running 7.0,.. (I hope to upgrade sometime in the near future)

I found that shutting the whole app. down and restarting works 2 out 3 times.

kumar · 28-01-2005, 12:03 AM

Hmm,,, this sounds familliar.... Ok, i always never run the modeller and layout at the same time... well when i was using 7.0.. that was because my ram was like 128 or 256... a very slow machine with built in video card... What i did was to save as another name... and the problem dissapeared.

19-01-2005, 03:36 PM	#1
timd Registered Member Join Date: Jan 2005 Posts: 2	Read-only objects? An object that I'm modelling has opened up today as read-only -- I can't do anything to it! Have i tripped a switch somewhere? In the Finder, Get Info shows the .lwo file to be unlocked... TIA, Tim

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
ok please read	keagan	Animation	2	01-01-2007 10:10 AM
Modeling objects; daily objects	pixelone	Modeling	1	05-09-2004 12:04 AM
please read	Kevin	Members Lounge	1	14-03-2003 07:08 AM
Please Read	Kevin	Site Questions & Suggestions	22	16-02-2003 10:44 AM

About Us

Beginner Training

Connect with

Need help? Email us

Popular Tutorials

Learning Paths

Useful Links

19-01-2005, 06:19 PM	#2
Mark Super Moderator Join Date: Jan 2003 Location: Sunbury, UK Posts: 2,339	Hmm... What version of LW? I think this is a known bug in 8.0. There's a number of ways you can work around it. The first is to simply copy the entire object, layer by layer into another one and save... tedious, and you might miss something such as maps, etc... but works. Another option to try is to run modeller without the hub (don't know how to do this on the Mac - on a PC add the switch '-0' (that's zero) to the command line) Hope this helps...

19-01-2005, 06:24 PM	#3
timd Registered Member Join Date: Jan 2005 Posts: 2	Thanks, Mark -- I'm using 7.5 (8.0 arriving this week). Will give the cut-and-paste a try.

27-01-2005, 10:24 PM	#4
Petrograde Full Access Member Join Date: Jan 2005 Location: Texas Posts: 29	I've had this happen a few times. I'm still running 7.0,.. (I hope to upgrade sometime in the near future) I found that shutting the whole app. down and restarting works 2 out 3 times.

28-01-2005, 12:03 AM	#5
kumar Full Access Member Join Date: Sep 2003 Location: Singapore, Posts: 913	Hmm,,, this sounds familliar.... Ok, i always never run the modeller and layout at the same time... well when i was using 7.0.. that was because my ram was like 128 or 256... a very slow machine with built in video card... What i did was to save as another name... and the problem dissapeared.