search

AngryAnt / Behave-release

The Behave project is a system for designing, integrating and running behaviour logic using Behaviour Trees for simulated characters in unity projects. NOTE: This project relates to Behave 1. For Behave 2 support and information, please use the AngryAnt community at http://community.angryant.com
http://angryant.com/behave
34 stars 6 forks source link

NotImplementedException: Resource streams are not supported from transparent code #73

Open t0chas opened 9 years ago

t0chas commented 9 years ago

Hi,

I do get an exception when running Behave1.4 BTs on PSVita

[7.072128] Device 1 matched profile PlayStationVitaPSMProfile (PlayStation Mobile) [7.139599] Joysticks: PS Vita [7.172131] AngryAnt Behave version 1.4 - Copyright (C) Emil Johansen - AngryAnt 2011 [8.133762] 0: fps 0.99 ms/f 1006.40 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 87462KB / 106496KB], [monoMem peak 400KB, curr 400KB of 468KB] [8.588575] NotImplementedException: Resource streams are not supported from transparent code at System.Reflection.Assembly.GetManifestResourceStream (System.String name) [0x00000] in :0 at Behave.Runtime.Resources.GetResourceStream (System.String resourceName, System.Reflection.Assembly assembly) [0x00000] in :0 at Behave.Runtime.Resources.GetByteResource (System.String resourceName, System.Reflection.Assembly assembly) [0x00000] in :0 at BLNewBehaveLibrary0.get_Data () [0x00000] in :0 at BLNewBehaveLibrary0.get_Library () [0x00000] in :0 at BLNewBehaveLibrary0.TreeAssetData (Int32 collectionIDX, Int32 treeIDX, Behave.Runtime.Tree tree) [0x00000] in :0 at BTNewBehaveLibrary0C0T0.get_AssetData () [0x00000] in :0 at BTNewBehaveLibrary0C0T0.SetActiveComponent (Int32 id) [0x00000] in :0 at BTNewBehaveLibrary0C0T0.Tick0 (IAgent agent, Behave.Runtime.Tree sender, System.Object data) [0x00000] in :0 at BTNewBehaveLibrary0C0T0.Tick (IAgent agent, Behave.Runtime.Tree sender, System.Object data) [0x00000] in :0 at Behave.Runtime.Tree.Tick () [0x00000] in :0 at AIAgent+c__Iterator0.MoveNext () [0x00000] in :0 [9.143523] 48: fps 47.54 ms/f 21.04 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 424KB, curr 424KB of 468KB] [10.144536] 108: fps 59.94 ms/f 16.68 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 460KB, curr 460KB of 468KB] [11.145540] 168: fps 59.94 ms/f 16.68 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 504KB, curr 504KB of 628KB] [12.146543] 227: fps 58.94 ms/f 16.97 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 548KB, curr 548KB of 628KB] [13.147528] 287: fps 59.94 ms/f 16.68 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 608KB, curr 608KB of 628KB] [14.149305] 347: fps 59.89 ms/f 16.70 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 608KB, curr 468KB of 628KB] [15.149831] 407: fps 59.97 ms/f 16.68 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 608KB, curr 560KB of 628KB] [16.150537] 467: fps 59.96 ms/f 16.68 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 608KB, curr 464KB of 628KB] [17.151506] 527: fps 59.94 ms/f 16.68 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 608KB, curr 512KB of 628KB] [18.152500] 587: fps 59.94 ms/f 16.68 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 608KB, curr 540KB of 628KB] [19.153487] 647: fps 59.94 ms/f 16.68 [kernel avail main 180MB, cdram 0MB, phycont 26MB], [vram avail 89510KB / 106496KB], [monoMem peak 608KB, curr 564KB of 628KB]

t0chas commented 9 years ago

Update: you were right this only happens with debug BT builds.