Home › Forums › Bug Reports and Feature Requests › Serious Issue Tabs / Puzzles gone
- This topic has 7 replies, 2 voices, and was last updated 5 years, 1 month ago by Yuri Kovelenov.
-
AuthorPosts
-
2019-09-29 at 5:21 pm #19463GLiFTeKCustomer
Hi.
I recently imported a lot of puzzle groups into a project from another project.
after that a bug happened where when ever i clicked on the variables menu it would only show a few crowded over each other on the top (i have A LOT of variables) … but none in the list..EXCEPT for the new Tab i brought all the new puzzles into.. there i can see the variables tab just fine…i was going to write about this but then a worse thing happened..
now when ever i open my puzzles files… there is nothing.
all the tabs are gone except the init and main.
librarys are gone also.
the puzzles are in the init.. only the custom fonts i load and then in Main .. main doesn’t even have the dot grid.what should i do?
i see everything’s intact by viewing my .js and .xml files in a code editor.
this is happening to ALL the xml files that have been backed up.. so it’s probable not the xml files but something else…hope this can be fixed
Visit the GLIFTEK Verge3D Plugins Store!
GLIFTEK.com for Plugin Documentation & LIVE DEMOS!
LIKE The GLIFTEK Facebook Page for updates!
Join the Verge 3D Discord Server!
plz share Discord link & on your signature!2019-09-30 at 5:56 am #19472Yuri KovelenovStaff2019-09-30 at 8:39 am #19498GLiFTeKCustomerHi,
any errors are printed in the browser console when you open the Puzzles editor? If you create a new default project, is it working with Puzzles?hi,
ok yuri. i checked.
this is what i get from console…
“Successfully compiled asm.js code (total compilation time 25ms) v3d.js
Error: Variable “all_buttons” is already in use and its id is “DWms@8@+uaeuc0l=^8Ng” which conflicts with the passed in id, “EwWiYp[#I%Sx80i!Qe59”. puzzles.min.js:1:429633″as far as creating a new default project…
nothing on console..
puzzles come up no problem everything available and in order.(also while testing the project that caused this problem… before.. console was giving me a LOT of (if i remember properly) .. warnings about something about a “false” somethings..
(using new pre 3, windows,8.1, firefox.)
thnx for attention to this.
(wouldn’t want this to happen to anyone )also.. “all_buttons” IS .. a var i used as a variable.. but then made it a dictionary. so it might be used as BOTH a regular var AND a dictionary somewhere…
tell me where i could go delete the var (non dictionary) version and i’ll see if i can get results. don’t know which file(s) to do that in though.
(i have plenty backup so this isn’t a Javapocalypse. )
(but would like to figure out it for future)
thanks!Visit the GLIFTEK Verge3D Plugins Store!
GLIFTEK.com for Plugin Documentation & LIVE DEMOS!
LIKE The GLIFTEK Facebook Page for updates!
Join the Verge 3D Discord Server!
plz share Discord link & on your signature!2019-09-30 at 9:09 am #19511Yuri KovelenovStaffError: Variable “all_buttons” is already in use and its id is “DWms@8@+uaeuc0l=^8Ng” which conflicts with the passed in id, “EwWiYp[#I%Sx80i!Qe59”.
Apparently you had the variable “all_buttons” in place before you imported a group of puzzles which also used that variable, and it broke. Looks like a bug of the Library feature to me.
I reproduced that misbehavior by adding a group of puzzles with a variable to the Library and importing it back with another project containing a variable with the same name. I was able to work around this by renaming the variable before importing (may be it’ll work for you).
Anyway, we’ll try to investigate it on our side and hopefully fix it. Thanks for reporting the bug!
2019-09-30 at 9:15 am #19512GLiFTeKCustomerError: Variable “all_buttons” is already in use and its id is “DWms@8@+uaeuc0l=^8Ng” which conflicts with the passed in id, “EwWiYp[#I%Sx80i!Qe59”.
Apparently you had the variable “all_buttons” in place before you imported a group of puzzles which also used that variable, and it broke. Looks like a bug of the Library feature to me.
I reproduced that misbehavior by adding a group of puzzles with a variable to the Library and importing it back with another project containing a variable with the same name. I was able to work around this by renaming the variable before importing (may be it’ll work for you).
Anyway, we’ll try to investigate it on our side and hopefully fix it. Thanks for reporting the bug!no problem.
GLAD to see you caught that thing there.
anyway, it’s better i start back on the project a few days prior, as there are things i would do better this time in implementing…plus, by resetting my browser, i can now actually zoom in on the puzzles to a visible level instead of not being able to read them haha..
but so i got to bring up those “fake” message errors i was getting…
and i’ll be using the project that’s giving me them ..
so i think they should be figured out as well..here’s the console reading JUST from opening…. (NO interactions made, at begininng) …
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Successfully compiled asm.js code (total compilation time 24ms) v3d.js
Verge3D 2.15.0 pre1 (WebGL 2.0) v3d.js:1:538394
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(119,8-63): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(123,10-65): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(134,8-60): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(93,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(97,25-100): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(119,8-63): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(123,10-65): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(134,8-60): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(93,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(97,25-100): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(75,12-96): warning X4713: Sample Bias value is limited to the range [-16.00, 15.99], using -16.000000 instead of -100.000000 v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(90,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(94,25-100): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(71,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(96,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(70,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(111,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(112,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(111,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(104,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them 4 v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(111,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(112,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them 2 v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(111,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(256,10-65): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(267,8-60): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(88,25-100): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect themVisit the GLIFTEK Verge3D Plugins Store!
GLIFTEK.com for Plugin Documentation & LIVE DEMOS!
LIKE The GLIFTEK Facebook Page for updates!
Join the Verge 3D Discord Server!
plz share Discord link & on your signature!2019-09-30 at 9:19 am #19515GLiFTeKCustomerok cool.
here’s the readout i have on my current version of my recovered project that i’m working on… the “fake” message…
(this is all at startup without interactions) .._____________________________________________________________
Successfully compiled asm.js code (total compilation time 24ms) v3d.js
Verge3D 2.15.0 pre1 (WebGL 2.0) v3d.js:1:538394
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(119,8-63): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(123,10-65): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(134,8-60): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(93,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(97,25-100): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(119,8-63): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(123,10-65): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(134,8-60): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(93,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(97,25-100): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(75,12-96): warning X4713: Sample Bias value is limited to the range [-16.00, 15.99], using -16.000000 instead of -100.000000 v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(90,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(94,25-100): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(71,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(96,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(70,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(111,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(112,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(111,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(104,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them 4 v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(111,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(112,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them 2 v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(111,23-154): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(256,10-65): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(267,8-60): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them v3d.js:1:473473
v3d.WebGLProgram: gl.getProgramInfoLog() C:\fakepath(88,25-100): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect themVisit the GLIFTEK Verge3D Plugins Store!
GLIFTEK.com for Plugin Documentation & LIVE DEMOS!
LIKE The GLIFTEK Facebook Page for updates!
Join the Verge 3D Discord Server!
plz share Discord link & on your signature!2019-09-30 at 9:30 am #19519GLiFTeKCustomerwhich file should i safely edit in my code editor, to remove the unwanted second use of the var?
.html? .xml? .js? ALL?
Visit the GLIFTEK Verge3D Plugins Store!
GLIFTEK.com for Plugin Documentation & LIVE DEMOS!
LIKE The GLIFTEK Facebook Page for updates!
Join the Verge 3D Discord Server!
plz share Discord link & on your signature!2019-09-30 at 10:10 am #19535Yuri KovelenovStaff -
AuthorPosts
- You must be logged in to reply to this topic.