search

bsimser / Inventory-Pro

https://devdog.io
MIT License
2 stars 0 forks source link

Errors importing asset into unity 2017.3 #256

Closed bsimser closed 5 years ago

bsimser commented 6 years ago

Original report by Anonymous.

Attempting to integrate into existing Unity project - when imported - compile errors and only option in"tools" is DevDog->check for updates - 7 errors:

Assets/Devdog/InventoryPro/Scripts/Modules/Triggers/AdvancedTrigger.cs(39,30): error CS0115: `Devdog.InventoryPro.AdvancedTrigger.CanUse(Player)' is marked as an override but no suitable method found to override

Assets/Devdog/InventoryPro/Scripts/Modules/Triggers/AdvancedTrigger.cs(68,30): error CS0115: `Devdog.InventoryPro.AdvancedTrigger.CanUnUse(Player)' is marked as an override but no suitable method found to override

Assets/Devdog/InventoryPro/Scripts/Modules/Triggers/ItemTrigger.cs(40,30): error CS0115: `Devdog.InventoryPro.ItemTrigger.CanUse(Player)' is marked as an override but no suitable method found to override

Assets/Devdog/InventoryPro/Scripts/Modules/Triggers/ItemTrigger.cs(56,30): error CS0115: `Devdog.InventoryPro.ItemTrigger.CanUnUse(Player)' is marked as an override but no suitable method found to override

Assets/Devdog/InventoryPro/Scripts/Modules/Triggers/ItemTrigger.cs(61,30): error CS0115: `Devdog.InventoryPro.ItemTrigger.Use(Player)' is marked as an override but no suitable method found to override

Assets/Devdog/InventoryPro/Scripts/Modules/Triggers/ItemTrigger.cs(88,30): error CS0115: `Devdog.InventoryPro.ItemTrigger.UnUse(Player)' is marked as an override but no suitable method found to override

SpeedTree materials need to be regenerated.

bsimser commented 6 years ago

Original comment by Joris Huijbregts (Bitbucket: jjahuijbregts, ).

Do you have any third party assets in your project? Most likely there's a class named "Player" that isn't namespaced and is, therefore, conflicting with Inventory pro.

bsimser commented 5 years ago

Original comment by Herman Tulleken (Bitbucket: herman_tulleken, ).

Not a Inventory Pro issue.