6 réponses à ce sujet

[AmstradHero]

Since installing version 1.0.1008.0 of the toolset, I can't move about in the level editor. I can zoom in and out with the scroll wheel, or zoom in and out with "w" and "s", or move side to side with "a" and "d".  But that's it.

I can't rotate the camera, I can't move the camera's focus in the vertical plane, all I can do is look at a little corner fragment of a level.

I can move the camera perfectly fine in any other editor within the toolset.

Has anyone experienced this, or have any idea what might be causing it?

I would appreciate any help in this matter, because until this is fixed, there's no way I can do level design.

[deadrockstar]

I sporadically encounter exactly the same problem. At first I thought it was my mouse, which I took apart and cleaned. Tried a (ugh) wired mouse too - same problem. Then I realised I couldn't rotate the camera using the ctrl-click method either. I'm not sure what causes it, but it is infrequent enough not to cause me any major headaches. Still very annoying all the same.



I don't know how to sort it, but just thought I'd give a heads-up that you're not alone.

[Gnasche]

The middle mouse button does all of the other kinds of movement, like panning. It can be used in conjunction with ALT. Sometimes you have to go into your mouse software and configure it for a middle button.

You can also edit DefaultSettings.xml to set the movement keys to anything you want. I'm not sure what folder that's in. I'm not at a computer with DA installed.

Modifié par Gnasche, 26 décembre 2009 - 05:21 .

[AmstradHero]

Gnasche, deadrockstar: This seems to be an issue with Logitech Setpoint in that sometimes it does not seem to register middle mouse correctly within the DA toolset..

Setpoint also falls short of the old MouseWare software as it doesn't seem to be possible to use the scroll-wheel click as a middle button - MouseWare would let you do that.



However, having mapped one of the extra buttons on my mouse to the middle button, I still occasionally hit this problem. If this happens, I just go into Setpoint, switch that button so it does something else. I apply that, then reset it back to using the middle mouse button. At that point, it works fine within the toolset.



So it's an annoying bug, but I've found a workaround now at least.

[deadrockstar]

Ah, that's interesting to know. I don't have a Logitech mouse, but I am running my mouse without any of the proper drivers or software. It has worked fine for years like this, but I might want to fire up the real software and try changing mappings when this problem occurs.



Thanks for the info!



Will look into the defaultsettings.xml too, I would like to change some of the movement keys.

[jtakemann]

I had this problem for my first 2-3 hours with the level editor, and I also have a wireless Logitech mouse. It's been working fine recently, though.



Changing the camera styles (the 2 dove buttons at the top) made it finally work for me. I'm not sure why it would... especially if it was a problem with the mouse. Perhaps it was an odd and happy coincidence and it fixed itself at the same time I was switching camera modes.

[Wulfeous]

anyone know the proper names for the back and forward buttons on a mouse to put into the xml?

I tried MB4 and MB5 but they had no effect. MMB is seriously uncomfortable to hold down after a while..