Errors on Importing Tactical Pro

[jkaczmar]

I'm getting a bunch of similar errors on importing Tactical Pro into my project. I believe I'm up to date with all the updates you've put out over the last couple of days. Here's the first couple of errors messages. I'm guessing the other might stem from these two initial ones:

Assets\Opsive\BehaviorDesigner\Add-Ons\TacticalPack\Scripts\Tasks\TacticalBase.cs(9,57): error CS0234: The type or namespace name 'Tasks' does not exist in the namespace 'Opsive.BehaviorDesigner.AddOns.Shared.Runtime' (are you missing an assembly reference?)

Assets\Opsive\BehaviorDesigner\Add-Ons\TacticalPack\Scripts\Tasks\TacticalBase.cs(18,42): error CS0246: The type or namespace name 'FormationsBase' could not be found (are you missing a using directive or an assembly reference?)

 

[jkaczmar]

Here's some additonal information on Assembly References. Not sure why these are missing, but I'm guessing it's at least one area causing the problems:

 

[Justin]

I mentioned it in the release notes but if you have the Formations Pack you will need to first remove the package and reimport. There were some structural changes which requires a complete reimport. I just imported the Tactical Pack and Formations Pack in a fresh project and it worked.

 

[jkaczmar]

It's a different problem. I don't own either Formations or Formations Pro.

Is the Formations Pro pack required for the Tactical Pro pack to work?

 

[Justin]

No, it's not required. Based off of those missing references it can't find the Graph Designer:


Can you try importing into a fresh project, just BD then the Tactical Pack?

 

[jkaczmar]

The basic install approach you outlined was enough to allow me to fix some problems by comparing across the two projects, but not all. I had to remove all BD Pro, packs, and integrations and reinstall across the board on my main project. This appears to have worked in that everything is working, including tactical. However, even the reinstall wasn't clean. I think you have some unintentional dependencies built into the products that will only come up in more complex environments that already have some components in place. Here's what I found on reinstall.

• Reinstall BD Pro--worked fine.
• Reinstall Movement--Installed but created bugs that prohibited compilation of the project. Had references to a bunch of stuff in Tactical, even though all BD pro components and packs were completely removed from Assets, Packages, including all integrations.
• Installed A* Integration--Installed.
• Installed Senses_installed.
• Install Tactical--Installed and fixed the bugs from Movement so that things now clean compiled.
• Installed UCC integration.

I think what you'll find is that others will have installation issues if they already have an in-flight project. It might be order dependent. In retrospect, I think that I could have probably fixed my problems by installing Formations as that is where the final unsolvable reference realted bugs were coming from. I'm not saying that Formations is required, just that the Shared directories seem to be creating unwanted dependencies depending on the order in which you install.

Might be worth tweaking some of the packages to check for unwanted dependencies. Giving guidance to remove everything from Assets and Packages is probably a workable backup for most users. I lost a few hours fiddling with things, but I didn't lose any work as my graphs all came back intact.

 

[Mr-Hyper]

The basic install approach you outlined was enough to allow me to fix some problems by comparing across the two projects, but not all. I had to remove all BD Pro, packs, and integrations and reinstall across the board on my main project. This appears to have worked in that everything is working, including tactical. However, even the reinstall wasn't clean. I think you have some unintentional dependencies built into the products that will only come up in more complex environments that already have some components in place. Here's what I found on reinstall.

• Reinstall BD Pro--worked fine.
• Reinstall Movement--Installed but created bugs that prohibited compilation of the project. Had references to a bunch of stuff in Tactical, even though all BD pro components and packs were completely removed from Assets, Packages, including all integrations.
• Installed A* Integration--Installed.
• Installed Senses_installed.
• Install Tactical--Installed and fixed the bugs from Movement so that things now clean compiled.
• Installed UCC integration.

I think what you'll find is that others will have installation issues if they already have an in-flight project. It might be order dependent. In retrospect, I think that I could have probably fixed my problems by installing Formations as that is where the final unsolvable reference realted bugs were coming from. I'm not saying that Formations is required, just that the Shared directories seem to be creating unwanted dependencies depending on the order in which you install.

Might be worth tweaking some of the packages to check for unwanted dependencies. Giving guidance to remove everything from Assets and Packages is probably a workable backup for most users. I lost a few hours fiddling with things, but I didn't lose any work as my graphs all came back intact.

I am having the problem you described with importing the Movement Pack for BD Pro. If the Tactical Pack is indeed required to make Movement Pack clean compile, how do I resolve the issue? I don't want to buy the Tactical Pack for BD Pro, don't really need it.

 

[jkaczmar]

I think you'll have to reach out to Justin on this one. He may have subsequently made some changes, but it felt like Tactical was required based on the error messages I was getting even though it isn't supposed to be. I definitely had multiple installs/reinstalls which may have affected my experience.

The first thing he will likely do is ask you to install the packages into a completely clean project to see if you still get the errors. If you've already done that, I would pass it along to him as a likely bug that may not affect all users for some reason. If it was universal, I think there would be a bigger outcry.

Sorry I can't give you more guidance than that.