3D Object Database Persistence w/CORS

[quentinpaden]

Images/Models not loading from database in OGV.

This is a big issue for loading 3D Models, and does not allow for the 3D object geometry viewing to be consistent or persistent.

Fixing this database persistence issue with firebase and a backend revamp of the mongoDB database.

[Gauravjeetsingh]

@Max2020q Can you explain this a little more? I don't think I get it completely.

What exactly is the issue? Do you see any error in console? Maybe post that.
When creating new issues, it's a good practice to always divide it into the following points:

• What is happening

• What should ideally happen

• Steps to reproduce

• Browser Info

• Possible Solution (if any)

[quentinpaden]

What is happening:

• 3D object not persisting on server in some cases, does not seem to load model
• Model preview not showing

What should ideally happen:

• Model should show in preview every time even when coming back to it later
• Model should show in thumbnail preview

Steps to reproduce:

• reload localhost on another browser and it doesnt seem to include loading info (in safari did not work)
• in chrome and mozilla it did work

Upon researching further the CORS issue doesnt reliably reporduce on safari and the models I'm testing load in chrome and mozilla now.

The issue I did find however was that most of the model was scaled so low that it didn't fully load in console until zooming in

[brlcad]

@Max2020q Have patience with my ignorance, but I don't feel like you've actually answered the main question -- what exactly is the issue? In describing "what is happening", you've described what's not happening but we need to understand WHY the model "does not seem to load" or why the 3D object is "not persisting" (if that's actually true) or if there's some other problm. If we don't know why it's not showing/loading/uploading/downloading/storing/etc, then there's no reason to believe changing anything will fix whatever the real problem is.

[quentinpaden]

@brlcad I would like to research further into this with another instance of safari and provide precise console logs from google chrome once I solve #89 today.