topic 1.6 asset browser bug in Stingray Forum (Read Only)

1.6 asset browser bug

Anonymous — Fri, 02 Dec 2016 22:59:50 GMT

After some edit-test run iterations it's impossible to drag and drop units from asset browser into level. The following error is being logged:

Editor / Level Viewport: Level Viewport (file:///W:/Steam/steamapps/common/Stingray/editor/core/directives/engine-viewport-npapi.js:146:20) unhandled exception, TypeError: vp.trigger_drag_and_drop_state is not a function
    at triggerDragAndDropState (file:///W:/Steam/steamapps/common/Stingray/editor/core/directives/engine-viewport-npapi.js:146:20)
    at endDragAndDrop (file:///W:/Steam/steamapps/common/Stingray/editor/core/directives/engine-viewport-npapi.js:166:17)
    at file:///W:/Steam/steamapps/common/Stingray/editor/core/services/marshalling-service.js:282:32
    at Array.map (native)
    at Object.RemoteObject.raiseRemoteEvent (file:///W:/Steam/steamapps/common/Stingray/editor/core/services/marshalling-service.js:281:67)
    at Object.MarshallingService._handleRemoteEventHandlerEventRaised (file:///W:/Steam/steamapps/common/Stingray/editor/core/services/marshalling-service.js:953:30)
    at Object.ChannelManager._received (file:///W:/Steam/steamapps/common/Stingray/editor/core/common/channel-manager.js:67:34)
    at Object.WebSocketWithArguments._onMessage (file:///W:/Steam/steamapps/common/Stingray/editor/core/common/web-socket.js:42:18)

Restart of the editor is needed to return to proper behavior.

Re: 1.6 asset browser bug

__ben__ — Tue, 06 Dec 2016 15:51:08 GMT

Could you please post exact steps to reproduce the issue? For example, "1) create new project based on the character template, 2) drag another instance of target into the level, etc."

Does the problem occur every time or intermittently?

Please also try clearing your C:\Users\[username]\AppData\Local\Autodesk\Stingray folder in case this is related to state left behind by a previous version.

Re: 1.6 asset browser bug

Anonymous — Wed, 07 Dec 2016 11:24:41 GMT

Basically the steps are:

1. create new empty level, add default floor unit

2. import static mesh from FBX, import textures (previously I'd put them into one /textures folder, but now I group them per unit to avoid 'thumbnail bug')

3. produce new material for mesh (from custom parent material - diffuse-alpha, normal, MRA textures), assign textures to material, save

4. in unit editor assign material to mesh, create collision shape (box), save

5. drag new unit into level

6. test-run level

7. goto 2

After some repetitions (from 15 to 30, unpredictable) the error happens and editor needs to be restarted.