incNav update, Gota leave something for AC tool.... Options

[BlancoGato]

When I first started working on a spike macro, I saw the incNav and thought "COOL! A Nav routine!". Of course those of you who have used it, know full well its very out of date.

I know there is also something out there called BidiNav (or something like it). But I'm stubborn.... I wanted what looked like official sample includes to work. So I've spent some time working on incNav to bring it up to date with AC Tool 4.4. I also fixed some bugs that made it act so strange.

That said, here is my new and improved incNav.mac. Enjoy! The next post will have a script that exercises all the functions within and takes you on a tour of Arwic!

Please leave me comments (good or bad)!

I've made some more changes (escapes mainly), and have decided on incNav2.mac as the name (thanks for suggestion ping!).

I believe there is still one Nav issue left, but for the life of me I haven't been able to figure it out. I suspect its lag, so its hard to track down. The symptom is the bug is that it turns the opposite direction then it should. The good part is the next loop will correct itself. This doesnt happen every time, so I suspect its lag or delay updating _ns _ew _x _y.
If I do figure it out, I'll post an update.

Updated to fix 4.4.2 bug.

Updated to added version number: 2.2

Attached File(s)

 incNav2.mac ( 0bytes ) Number of downloads: 305

 

[BlancoGato]

TAKE A TOUR OF ARWIC!

Requires AC Tool 4.4 and the updated incNav.mac on the previous message.
Start the script after exiting the subway surface portal.

Updated to reflect usage of incNav2.mac.

Attached File(s)

 incNavTestRun.mac ( 0bytes ) Number of downloads: 29

 

[Ipa]

Late with me (1:30 am PST), so I can't test/review in detail until morning ... but congrats, and thanks for picking up a project that the macroing community needs and adapting it to the latest ACTool features.

Only suggestion I have right now is to rename it. It's your effort, call it "incBlancoNav.mac" (or something more creative), but you really should rename it to distinguish it from previous generation nav includes.

Include files are part of what builds the ACTool community. Thanks for contributing

[BlancoGato]

incNav is partially broken now (I assume $CharacterName is now depricated). I figured it was better to just update it. 90% of it is the same, so I don't have a problem with keeping it the same name (and I don't need the credit).

I don't know if the original author is around, but his comments would be appreciated as for the name.

[Ping]

Why not just name it incNav2.mac?
That would up the version number of it for easy identification.
As for credit, can't Blanco stick a comment in it for name and last time updated?

Just a thought.

[BlancoGato]

There is a compute bug in 4.4.1 and 4.4.2 that will cause this include file to report a compute error. I've made a change suggested by Ipa to work around this issue. This change has been verified on 4.4.0 and 4.4.2. It has not been tested on 4.4.1. If you have a problem with 4.4.1, then please upgrade. I don't believe this change will affect anything going forward.

PLEASE RE-DROP this include if you've already download it.

Thanks!

[Ipa]

QUOTE

PLEASE RE-DROP this include if you've already download it.

User save locations were a royal pain with incUI. The problem being that you can't guarantee where people will download the file to - sometimes its to their personal folder where they store macros ("My Documents" etc), the ACTool folder, the ACTool "macros" folder, even the Windows desktop.

What you can do to save some grief is add a version number Constant to your include, and Sendtext the version number. Really helps with support issues. Also helps macro authors who use the include, who can add a version check and pop an error and stop their macro if the correct version of your include isn't being included.

[BlancoGato]

Good idea Ipa. Btw - is there a way to detect the AC Tool version number? A quick scan of functions/variables didn't turn anything up.

[Ipa]

The variable {ActVersion} was just recently added - it's not in the help file yet, but should be documented in the ACTool readme.txt.

[BlancoGato]

Do you happen to know what 4.4.0 is equal to? I want to enforce 4.4.1+ because of MoveAllItemsVendor timing fix.

[Ipa]

The variable didn't exist in 4.4.0, so I expect a 4.4.0 macro would interpret {ActVersion} as a literal string '{ActVersion}' instead of substituting a number for it.

This *might* work

CODE

If {ActVersion} Contains ActVersion   SendText 13, Your version of ACTool is so old it doesn't even know what version it is. Upgrade NOW !!! End

[BlancoGato]

I guess that means I have to wait till I get home and test it on my machine that I left 4.4.0 on...

Unless someone out there wants to tell me what {ActVersion} reports on 4.4.0?

[Ipa]

I have 4.4.0.

Confirmed, it reports the literal string '{ActVersion}', so that code sample above should work.

[BlancoGato]

Cool, thanks.... Time to update some scripts!

[Luv2Macro]

Bumping this to the front page so people don't have to search for it if they want to use it in the fishing macro.