Hail. I have a recall out problem.
I noticed a red approaching when I was hunting monsters in dungeon, so I casted recall and targeted a recall rune in my backpack, then it said "Target cannot be seen."
A red started to attack me. I managed to get away of his range and casted recall and target a rune. It said "Target cannot be seen" again.
Finally I got killed
This problem happens quite often when I'm trying to recall.
Whenever it happens, I get owned by reds.
It might not be serious problem for blues who takes no risk. But...what if it happened to reds who takes skill/stat loss risk when they're trying to escape from bounty hunters? It must be serious problem for them.
Anyone else have the same problem?
"targetting lifebar bug" also happens to me.
viewtopic.php?f=8&t=21951&hilit=target+cannot+be+seen
***Using recommended version of Razor and UO client.
"That cannot be seen" when I targeted marked recall rune.
-
- Posts: 12
- Joined: Tue Jan 18, 2011 5:09 am
- Location: Japan
-
- UOSA Subscriber!
- Posts: 3367
- Joined: Sat Jan 30, 2010 12:01 am
- Location: In your tree house with binoculars
- Contact:
Re: "That cannot be seen" when I targeted marked recall rune
Go to the UO options screen, click on the mouse icon (top right), and check the option to "Run Mouse in a separate thread"
Sometimes you actually click through your target as if were transparent. This mouse option may help.
Edit: after reading through the old thread linked in the OP, this UO option probably wont help at all.
Sometimes you actually click through your target as if were transparent. This mouse option may help.
Edit: after reading through the old thread linked in the OP, this UO option probably wont help at all.
-
- Posts: 12
- Joined: Tue Jan 18, 2011 5:09 am
- Location: Japan
Re: "That cannot be seen" when I targeted marked recall rune
Thank you for your advice.Rose wrote:Go to the UO options screen, click on the mouse icon (top right), and check the option to "Run Mouse in a separate thread"
Sometimes you actually click through your target as if were transparent. This mouse option may help.
Edit: after reading through the old thread linked in the OP, this UO option probably wont help at all.
But I had already checked the option before I got PKed.
Hmm...I don't know why it happens.
Auto-recall-macro recorded with Razor also doesn't always work.
Re: "That cannot be seen" when I targeted marked recall rune
The reason that you're having problems with both targetting a life bar and targetting a rune is simple. You're client is not synchronized. It happens a lot on this shard for whatever reason, but there isn't a really a fix for it you can do on your end. The best thing for you to do is to create a convenient hotkey that "desynchronizes" your client. It can be found in razor under the hotkey tab.
Going forward:
-Cast recall
-While you're casting recall immediately press your new desync button
-Target rune when the target appears.
This will help you get away every time unless I decide to start playing again in which case it won't help you.
Going forward:
-Cast recall
-While you're casting recall immediately press your new desync button
-Target rune when the target appears.
This will help you get away every time unless I decide to start playing again in which case it won't help you.
-
- UOSA Subscriber!
- Posts: 2567
- Joined: Sat Oct 23, 2010 12:42 pm
- Location: Trammel
Re: "That cannot be seen" when I targeted marked recall rune
Sometimes, you have to physically close the client. It depends on several factors. Typically, just re-syncing will work, though.
Its a problem that's been around for a long time.
Its a problem that's been around for a long time.
[20:08] <@Kaivan> We have a ridable Maahes in Green Acres.
[10:00] <TheBreadman> leeds did a takeover on secondage
[10:00] <@Derrick> hax
Tom: Get bad bro