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
After many days trying to fix issues with XML to JSON, we gave up. There were two deal killers:
The trick used to speed up the gbXML pasrsin inevitably failed in some instances. After days trying to figure out where the error occurred, I think I have to place the blame on some issue deep down in the Three.js code - in a place far deeper than my skill level allows me to deal with.
The gbXML to JSON conversion as currently implemented simply takes too much time.
Because of these two issues. I decided to revert to code more similar to that in SGV r17.
But no sooner had I started the revert, I discovered all sorts of neat trick to add speed, simplicity and robustness. After a number of days away from XML, I cam back to it with a new sense of an ability to hack it and play with it.
The text was updated successfully, but these errors were encountered:
@GreenBuildingXML/core
https://www.ladybug.tools/spider-2020/spider-gbxml-viewer/
After many days trying to fix issues with XML to JSON, we gave up. There were two deal killers:
Because of these two issues. I decided to revert to code more similar to that in SGV r17.
But no sooner had I started the revert, I discovered all sorts of neat trick to add speed, simplicity and robustness. After a number of days away from XML, I cam back to it with a new sense of an ability to hack it and play with it.
The text was updated successfully, but these errors were encountered: