Forum Replies Created
-
AuthorPosts
-
eabrosiusParticipant
Sorry guys I’m not sure how to interpret this feedback exactly. Are those red-text Texture-related messages indicate that those particular png files are too large, not the ideal dimensions, or something else?
And then as far as the triangles rendered message… do I need to look into how to use Blender to reduce the complexity of my blender models so that there are less triangles rendered?
eabrosiusParticipantI have several other Verge apps that are working fine on iOS. I don’t know anything about cross domain violations, but if that’s the case for this app I would think it would also apply to my other apps wouldn’t it?
eabrosiusParticipantFound this thread because I’m experiencing this exact issue on iOS all of a sudden.
Running Verge 4.7. App is updated. Working fine on desktop.
I have disabled almost all of my “print to console” prompts. I have deleted all Camera and Light objects out of all of my Blender models. I have the “Compress Textures” box checked in the Verge3D Settings on Blender for all my Blender models.
I have cleared my iPhone’s entire browser history on both Safari and Chrome, still getting this error message (“A problem repeatedly occurred…”).
Link to app: https://v3d.net/54d
Screenshots attached.
App zip file is 207MB so I can’t attach to this post.Attachments:
You must be logged in to view attached files.eabrosiusParticipantVery nice, thank you!
eabrosiusParticipanteabrosiusParticipantI don’t see anything notable in the Console…? Also that tread shown on the stairs uses the exact same material in blender as the portion of the cupholder that is pink. How can one show up correctly if I’m missing a texture?
Attachments:
You must be logged in to view attached files.eabrosiusParticipantThis code has worked for years, and in the latest version of Verge it doesn’t, so if I want to update to the latest version I have to go find every instance where I’ve used this approach and fix it. Just wondering why…? Unless I’m understanding something incorrectly.
Attachments:
You must be logged in to view attached files.eabrosiusParticipantSo anyone that uses a loop to search through a list to find a specific item and then breaks out of the loop once they’ve found it now has to make sure to manually go back to every single search function they’ve ever written and save the found item as a new variable in order to continue delivering a functional product to their customers? What on earth triggered the idea to implement this change and what were the pros that could have possibly outweighed the cons in that decision making process?
eabrosiusParticipantUpdate: started working normally again
eabrosiusParticipantUpdate: when I load a backup xml file from the puzzles_backup folder, the puzzles display properly. The backup file is 2831 KB, which is only 8 KB smaller than the current version xml file (2839 KB).
Could it really be the size of the file that is causing this issue?
Not sure exactly what code I have added, so would prefer to not have to revert back to this old version. Also still concerned that this will happen again once the file size gets too large…
eabrosiusParticipantFigured it out. Haven’t cleared out my puzzles_backup folder in quite a while
eabrosiusParticipantThank you! Sorry for the rookie question. Still getting familiar with all of the available puzzle options. Glad you were willing to help!
-
AuthorPosts