Architect Archive
Thread: Item Movement Error
Page 1 of 2
bmf5000
Mon Oct 04, 2004 10:59 am
#1
Im an Interior decorator and I currently have several clients that would like me to decorate thier houses/shops, but the last couple days I have been getting an error with the move up command. The system no longer seems to recognize the command string in the macro I wrote, nor does it work when I type it out the long way. I can move things forward and backward, roatate works too, but not up. I was using the macro for months prior to this, and had made no changes.
I logged out for a few hours to see if it would correct itself, and then found it still broken. I came back the next day, still broken. Past running a full scan, which Im about to do, I dont see any other way to fix this?
Are my days of interior designing coming to an abrupt end?
bmf5000
Mon Oct 04, 2004 11:18 am
#2
Well, CSR helped me out and here's the fix:
The command line I was using was "move up 10"
The command line needed to be altered to "movefurniture up up 10"
Pawlin
Mon Oct 04, 2004 11:19 am
#3
I've had one instance where I wasnt' able to move someting up. I had dropped a painting in my house and it would let me move it any direction but up. I picked it up, went to another room and was able to move it up. I don't know what caused it. There wasn't anything else in the house to interfere with it.
If you have the problem with moving something up, try picking up the item then going to another room and see if it still happens with the same object.
Pawlin
Mon Oct 04, 2004 11:20 am
#4
bmf5000 wrote:
Well, CSR helped me out and here's the fix:
The command line I was using was "move up 10"
The command line needed to be altered to "movefurniture up up 10"
Huh? Did they change something? I know I've used "/move up x" all the time.
Ripchi
Mon Oct 04, 2004 1:34 pm
#5
I had this same problem at one point. I sent a bug report and a ticket on it. They said it was a known issue in certain areas and certain houses. They said if /move up x wasn't working, to use the radial menu or /movef up up. (Don't use a number with /movef up up).
Both of those options worked for me. The radial would move up 1, the /movef up up would move up 100, and then you can use /move down x to adjust down from there.
When /move up x wasn't working I'd get a message saying the correct command was /moveFurniture up x, but that never worked for me.
So for me, I use...
/move up x (where x is equal to 1 - 500)
...and if that doesn't work...
radial menu (equals /move up 1)
/movef up up (equals /move up 100)
EDIT: Oops, forgot the "f" in the /movef up up command...
Message Edited by Ripchi on 10-05-2004 01:31 PM
Splaktar
Mon Oct 04, 2004 2:57 pm
#6
This has been a problem for me for 3 months now. I've always had to use /movef up up #
PsychoticChipmunk
Mon Oct 04, 2004 3:19 pm
#7
Just hit me in a friends house but not in a couple other places. Could be another house bug like when /move back wouldn't work but forward would and vice versa on a few homes.
Typing out /move "name" up 1-500 works to get 'er up there.Odd thing is/move down works just fineso I basically just overshoot and use my down 1 macro to accurify it. This leads me to think it's the same or at least similaras the old bug just in the up commands now instead of for and back. Dunno but it's just a bit more of an inconvenience then normal.
Elyssa
Tue Oct 05, 2004 12:22 am
#8
I've use that all along, too.
Did you try using the full command /moveFurniture to see if that made a difference?
bmf5000
Tue Oct 05, 2004 10:31 am
#9
The problem apparently stems from certain houses, or so I was told. The only command that I saw affected was: /move up #.
I had a macro set with two commands, one was up 10, the other was up 2. Neither worked.
The fix was the extended coding: /movefurniture up up #
I reworte my macro, and now it works just fine. If your into interior design, I would suggest just changing your up macro to this to avoid an issue.
Pawlin
Tue Oct 05, 2004 11:16 am
#10
Interesting. Well I'll add somethign to the FAQ on this. Looks like enough people have seen it and there appears to be a good workaround.
Bandola
Tue Oct 05, 2004 11:24 am
#11
this may sound daft, but next time you try the /move up command, check the house you are in to see if there is an item called 'upholstered chair' anywhere close (I suppose it may also be in a neighbouring building if that is close enough), the 'up' from 'upholstered' could be causing the problem. 
if the command /move up is used under these circumstances it is possible that 'up' merely tries to target the 'upholstered chair' and then finds no further instruction, or cuases some kind of syntax conflict. Not saying this is it, but could be worth checking if you get the chance.
Alternatively, you could find a location where /move up works fine, then drop an upholstered chair nearby and try again. All in the interests of science, it would be nice to find an answer to this problem.
Message Edited by Bandola on 10-05-2004 11:31 AM
Pawlin
Tue Oct 05, 2004 11:36 am
#12
Good point Bandola. Thats another possible cause.
I know for sure that there wasn't an upholstered chair in the house I had the problem in.
Skullface65
Tue Oct 05, 2004 1:08 pm
#13
Yes if you have the wall targeted it will move up. 
/move a up 25 will move the targeted object up 25 units.
Page 1 of 2