alibaba / alibaba/G3D

framebuffer not ready

Open
#37 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
1.1k
Forks
110
PR merge metrics
No merged PRs in 30d

Description

![image](https://user-images.githubusercontent.com/38022455/99042196-4f0e7800-25c7-11eb-91b7-4f448cacb24f.png)
```
g3d_test() {
/*获取元素引用*/
var ganvas = this.$refs["gcanva"];
/*通过元素引用获取canvas对象*/
var canvaObj = enable(ganvas, {
bridge: WeexBridge
});
console.log(canvaObj)
console.log(G3D.Engine);

const engine = new G3D.Engine(canvaObj);
console.log(engine)

const scene = new G3D.Scene(engine);
console.log(scene)
},
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Begin at the g3d_test entry point, especially the enable(ganvas, { bridge: WeexBridge }) call and G3D.Engine construction shown in the issue. Reproduce the framebuffer-not-ready state and trace initialization through Scene creation; done means the supplied setup reaches a ready framebuffer without the reported failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.