What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Flying stops and corrects altitude

L

LaoArchAngel

Member
Joined
Oct 14, 2010
Messages
101
I'm sure I'm doing something wrong, but I don't know what. Hoping someone can put me in the right direction.

When I am farming with GB2 (at least on my Druid), and he's flying from one hotspot to another, he will occasionally stop moving, fly down a few feet (almost as if correcting his altitude), and then continue. It happens very regularly. I tried modifying the "height modifier" setting in Bot Settings, but this had no effect (no matter how large I went, positive or negative).

My profile is custom (made using RoutesBuddy). However, I get the feeling I'm not the only one seeing this. can anyone point me in the right direction?
 
The short answer is that, yes, I've seen it happen in other (public) profiles, but it doesn't happen in all of them (and it doesn't happen in all of mine, either). It usually happens in profiles with a lot of change in terrain.
 
So errrrr.... what exactly is the problem then? Why is this a problem? Does this result in the bot not gathering anything?
I'd say this is normal behaviour as GB will normally attempt to fly at a certain altitude. If the terrain suddenly changes, he'll have to suddenly change altitude. I don't see why this is a problem really.
 
what you are describing its not normal
try one of my profiles and tell me if you have the same problems
 
The reason its a problem is because the bot definitely looks robotic. No one seeing the effect would believe a human is controlling it.

@Tony: will do. Assuming that the problem does not persist with your profiles, what would you think is causing this issue? Do you think the z coordinate in my hotspots is too high / low? Normally I would investigate myself (and I will) but I'll be at work today and won't get a chance until this evening.

Sent from my Galaxy S II.
 
as an example
if the profile was recorded using a low speed mount might cause problems etc

waiting for your feedback
 
Lao, I saw that when I was using RoutesBuddy too although the last update he did seemed to make it at least somewhat smoother.

I decided to go a different route though - just by a little. I saw the tutorial on using the ZapRecorder and decided to give it a try. It's not difficult to use and since I can literally fly the route myself, I make the turns and height changes more gradual. I'm not making a commission off of this ;) and certainly not trying to 'dis' RoutesBuddy. I really like it... but I also liked that I can make my route my own and it just 'feels better' when I watch it.
 
Thanks for the heads up, Altoids. I also saw ZapRecorder and will be trying it. First, however, I am really interested in discovering what is the cause of this bug. I'm curious as to how/why a different mount speed would affect the performance of a profile. I believed that a profile, being a series of points, did not contain any velocity-specific data. I assumed that, given two points, the bot would calculate the necessary direction (including angle) at which to travel and make modifications en-route when coming across obstacles. Obviously that is an over-simplification of pathing, but that was how I figured flying would work from a high-level POV. Apparently, this is not the case. I'm guessing right now that the Z coordinate in the profile (probably modified by RouteBuddy's Height option) is a lot more important than I'd originally thought. I especially think this because changing the "Height Modifier" property in my Bot Configuration currently has absolutely no effect what-so-ever (I tried -300 and 300). I think that the coordinates in my profile might be off by so much that the bot has to disregard the Z coordinate, my height modifier, and calculate the Zs on-the-fly based on the mesh/pathing. Of course, all of this is speculation until I get home and datamine + run some tests.

I don't mean to sound flippant about your suggestion, Altoids, because I will be using ZapRecord (I think I already have it installed, actually). It's just in my nature to want to figure this out before I move on. It's in my head. Gotta get it out. :)
 
ZapRecorder is not the best option

i got many reports for bugged profiles from this tool
 
Follow on silly question #1 then... uh... what's the trick to creating them in GB1? (or to put it another way... is there a simple tuturial for getting familiar with GB1 cause I have literally never even touched it... not sure how to even turn it on... of course, I'm at work right now and can't even try right now - but that will change within the next hour... *sly smile*
 
Yeah, using GB also crossed my mind (my initial thought was to try converting by HB profile to GB and trying it there, but this sounds cleaner). However, I loaded it long enough to realize I was trying to use the wrong type of profile and that the GB I was looking for was plugged into HB. Anyway, I'm going to go study the wiki's instructions for creating a new profile in GB1, but if you have an ace up your sleeve you'd be willing to share, I'd take it as a kindness if you did. :)
 
I'm on my way home in about 30 mins... and will probably look the Wiki over myself to get it fingered out... ;)
 
Victory! So, I decided to take a peak inside of the profiles created by RoutesBuddy. Sure enough, right after creating a profile, the plugin sets the Z to whatever you set the Height value. By default, this is 80. I'd set it to 0 for testing. Today, I re-created the exact same route, but then I went into the profile and did a replace all of 'Z=".*" /> with 'Z="380" /> (I used the Development Tools to check my height @ right above the tree-line).

The result was that the bot stopped correcting the altitude every few feet. Occasionally the bot will fly straight down to get to a node, but I do that, too, IRL, so it doesn't look unrealistic IMHO.

My conclusion is that if Z is set too low, HB will set a default flying height above the ground, but will then adjust for every little "nook" in the terrain. The "easy" fix is to set the Z coordinate to whatever height you want to fly @ and set the height modifier in Bot config from there. The "good" fix is to, as Tony suggested, build your routes in GB1 and then convert them to GB2.

Also, just as a heads up, the max "height" you can set it to in RoutesBuddy is 200. You can add an additional 300 on the bot (or subtract, as the case may be).
 
You must log in or register to reply here.
Back
Top