[solved] Upgrading view3dscene 3.18.0 to Castle Model Viewer 5.2.0

3D
1

Hello,
I’m looking for some help… in May 2000 Raymond Tweety, retired former NASA animator, wrote a piece of VRML 2.0 code for the Southwest Mural Project (a joint project of the Peabody Museum at Harvard, the Museum of Northern Arizona, and the Hopi Cultural Preservation Office). He had us use COSMO Player to open a file which displayed the interior of a series of Hopi Kiva rooms… the Peabody Museum shot over 2,000 3 1/4 x 4 1/4 photographic negatives of the archaeology on the Hopi’s Awat’ovi Mesa between 1935 and 1939. Originally photographed in black & white (because Kodak didn’t make color film for that size camera), these negatives have been scanned at high resolution, colorized (and color calibrated… the photographer kept a running list of Dictionary of Color notations) and entered into an ACCESS database.

“tDAR”: the National Digital Archaeological Records Archive Center at the Arizona State University has recently uploaded the Southwest Mural Project Database which contains over 700 images of Hopi Kiva murals along 5,546 records (several images per record) of Hopi Yellow-ware pottery. Four years ago I discovered that COSMO Player no longer worked with anything higher that Window 8.0 and downloaded view3dscene 3.18.0 which worked fine. We have recently discovered that we do not seem to be able to successfully upgrade to Castle Model Viewer 5.2.0… a room opens, but all the walls are white. I have tried using ChatGPT to upgrade the code… now the walls are black.

HELP… my name is Steve Erdmann… my email address is serdmann@earthlink.net
I can attached the original file if anyone out there is interested… it’s only 27K

2

Hello,

There has been a ton of changes since version 3.18.0 to current 5.2.0 :slight_smile: It is possible we introduced some bug, in which case: I’m sorry, and we can fix it!

Please submit a testcase (input 3D model) that shows the problem.

  • Preferably not your full model, but only a subset of it, that demonstrates the bug. With all textures etc., everything that you can share.
  • If you have a screenshot from old COSMO Player and/or old view3dscene 3.18.0 showing the proper rendering, also please send it.
  • If you can, test it also in the latest “snapshot” Castle Model Viewer version 5.3.0 downloadable from Castle Model Viewer page. It has a lot of additional work (and some fixes) over the last 5.2.0.

If you are OK with sharing your model publicly, you can send it here (attach to a post on this forum) or create a new issue in our GitHub project.

If you don’t want to share it publicly, but are fine to send it privately to me, then please send it to michalis@castle-engine.io. Some other ways to contact me privately are listed on https://michalis.xyz/ . Of course I will only use your model for the purpose of investigating the bug.

Thank you!

AI tools are sometimes helpful, sometimes dumb :slight_smile: We have recently posted guidelines about using AI, which may be of interest: Using AI when contributing to Castle Game Engine | Manual .

3

I’m making a note here, for everyone reading the forum, that we solved this privately :slight_smile:

Public outcome: See test of Material.shininess to know how it affects materials:

1 Like