On Fri, Oct 20, 2017 at 5:22 PM, Alan Etkin <[email protected]> wrote:
> Well, I suppose it is the ancient pc's fault > > Processor: (32 bit) Sempron LE-1250 2.2 Ghz > RAM 2 Gb > Graphic card: GeForce 8200 > Windows 7 > > hmm... That would be from ~2006, win XP or starting win Vista. I would suspect the drivers, but you can't do much about that... A thing you can try is moving the RESOUCE(...) after the director.init, having the visible window hopefully means the texture load will go into the visible window openGL context, and not in the shadow window shared context. Just try, it is easy. > The same issue with a newer system but running on virtual box (Win 10) > > VMs are tricky for games (timing issues, the guest host talks to virtual drivers which talks to the host drivers...), by example https://apple.stackexchange.com/questions/246251/opengl-2-0-on-windows-10-on-virtualbox-on-el-capitan By the way, the second answer solves gl problems with Blender, may be you can repurpose for pyglet (at your own risk, I never tried to run a game in a VM) > Daniel's approach works fine. The problem comes when you want to call > pyglet.resource methods outside a node constructor > > Thanks > > > -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/cocos-discuss. For more options, visit https://groups.google.com/d/optout.
