You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually, I can't seem to get Tracegl working at all. I even created a very simple app to test with just an index.html page and a single js file with a simple alert in it. I'm using Chrome v. 29.0.1547.66 on a Windows 7 machine.
I only purchased this today. If I can't get it working then it doesn't even help me solve 1 bug, and therefore is definitely not worth the few cups of coffee it cost me.
I sent an email yesterday, and this is the response I got:
"Hi Ishmael,
Yeah this problem is caused by a fix for other videocards, i have no easy way to detect which type you are to switch. I can try to get you a custom build, let me think about it."
Activity
greglockwood commentedon Jul 16, 2013
I was initially able to get it working with Firefox 22.0, but not in Chrome or Chrome Canary on Windows.
hex commentedon Aug 19, 2013
I have the same problem.
On Windows 7 x64 with Chrome Version 29.0.1547.0 dev-m
HeikoR commentedon Aug 21, 2013
Same problem here:
Windows 7 x64 with Chrome Version: 30.0.1599.10 beta-m
Volox commentedon Aug 28, 2013
+1
wridgers commentedon Sep 4, 2013
👍 Same problem here!
robindexter commentedon Sep 11, 2013
Same Problem, Win 7 ,x86, Chrome Version 29.0.1547.66 m
IngageStroliaC commentedon Sep 24, 2013
Same here.
Actually, I can't seem to get Tracegl working at all. I even created a very simple app to test with just an index.html page and a single js file with a simple alert in it. I'm using Chrome v. 29.0.1547.66 on a Windows 7 machine.
I can go to the app with http://localhost:2080, no problem, but I can not get http://localhost:2000 do show me anything but the error:
I only purchased this today. If I can't get it working then it doesn't even help me solve 1 bug, and therefore is definitely not worth the few cups of coffee it cost me.
ishmaelthedestroyer commentedon Nov 16, 2013
I'm getting the same issue. A blank page pops up on Chrome, but it seems tow ork fine with Firefox. Any fixes?
wridgers commentedon Nov 17, 2013
It's been a long time now. Frankly I'm a bit irritated. I bought tracegl only to immediately encounter this bug.
The developer appears to have abandoned us.
ishmaelthedestroyer commentedon Nov 17, 2013
I sent an email yesterday, and this is the response I got:
"Hi Ishmael,
Yeah this problem is caused by a fix for other videocards, i have no easy way to detect which type you are to switch. I can try to get you a custom build, let me think about it."
I'll post any information I get on this thread.
martindale commentedon Nov 19, 2013
+1 on this, having the same issue.
Version 33.0.1707.0 dev-msindresorhus commentedon Nov 19, 2013
+1
matt-wratt commentedon Nov 27, 2013
+1
matt-wratt commentedon Nov 27, 2013
My work around was to use Firefox
ncote commentedon Dec 7, 2013
I wouldn't mind having to specify the card explicitly if it can get it working...
owenyang0 commentedon Jan 3, 2014
+1
cristiano-belloni commentedon Jan 18, 2014
+1 here. Macbook pro,
Intel HD Graphics 4000:
Chipset Model: Intel HD Graphics 4000
Type: GPU
Bus: Built-In
VRAM (Total): 1024 MB
Vendor: Intel (0x8086)
Device ID: 0x0166
Revision ID: 0x0009
Displays:
pixelshaded commentedon Jan 22, 2014
+1
AMD Radeon HD 7570M
ardcore commentedon Feb 27, 2014
+1!
Uncaught Error: Could not link, max varying:15
Chrome 33 / OSX, Intel HD 4000
hulkish commentedon Mar 9, 2014
Should I assume this issue will remain unresolved? Having the same issue here..
emnh commentedon Mar 17, 2014
same issue
emnh commentedon Mar 17, 2014
got it working by workaround of commenting out the exception throw as suggested, and inserting a "return" at top of trace.gl update function
hulkish commentedon Mar 19, 2014
The change from @emnh also worked for me