I just checked on my end, T-Mobile ISP. I cleared cache, Chrome new incognito, disabled cache in networking and it fails again. This time I can’t get to the main page. The cookie question pops up, but the moment it does, the white screen replaces it (with only the cookie-question icon showing). Firefox works fine.
In closer inspection, a dynamic JavaScript, “CuKSISK.js” lists a content-type: text/javascript in Firefox, but in Chrome, the same js has no listing for content-type in the response headers.
The dynamic script names change every now and then, but the same issue of not listing a content-type for one or more scripts in response headers is consistently present in Chrome. I have sent such logs/screencasts/etc. to support.

Firefox browser will work as Maxon troubleshoots.

Dr. Sassi, the biggest issue for me as I was working with Support Team was that they couldn’t see anyone else having the problem, and that they couldn’t reproduce the error. Please let them know about these other reports from the eastern USA. Perhaps they will narrow it down.

Yes, this is the exact issue I have. However, may have narrowed it down to a smaller .js file and that file not having their MIME-Type set. All of the other scripts have a proper MIME, but this one does not:
I see errors in 3 .js files:
CyjJQS-n.js
DcQYf4Dz.js (MIME TYPE is not listed under Chrome/Safari. But in Firefox it is shown as Text/javascript)
B_4WZ4t6.js

This is exactly the error I see here in SC.

One of the challenges from support was that they only had my support ticket on this subject. While I tested on countless systems/networks, they could not reproduce the problem. When I sent several videos of me asking completely random people to try on their network, I think they had a starting point. I say this so affected users will actually open a support ticket and let them know as much as possible about browser/ISP, etc. I know IT can be tough, so perhaps this will help.

Hey CSpill, I am the one who reported it. I am in the southeast USA. Please pass on as much of your situation to the support staff at Maxon. Perhaps if they discover others who have reported the issue, they can narrow it down. I have been getting help, but it still hasn’t worked completely.
I did find a work-around. If I use the Firefox web browser, the site loads fine. I have many theories, and have shared them with support, so hopefully they will be able to figure it out.
Try Firefox, it may work in the meantime.

Thanks again. I did not know about the zip file restriction. I made the .har Google Chrome archive, but I couldn't upload it to the Zendesk on the support-side ticket, so I tried zipping it. I have uploaded the original .har file to the google drive share above and the rtf file which explains what my research discovered.

I want to thank you for your rapid response. Indeed, your patient and kind responses are the gold standard in support.
As I walked into work today, I asked a random person to try their cell phone to browse to the site. It failed on their Verizon iphone using Safari just as it does on several networks.
I would like to share the video screenshot I have to show the error, along with the google chrome html archive. I also have a .zip file which has a possible explanation of why this occurs at only certain locations.
Would you be willing to pass the files on to your IT Personnel?
https://drive.google.com/drive/folders/1-tqr1yz-MclnYLNl3N_hpiaFrqiLHS2s?usp=sharing

I cannot get Cineversity to load any sub pages on several networks here in the USA. For more than 15 days, the issue happens at the school’s AT&T network as well as TMobile WiFi or cellular or at several locations. I was able to get it to work when connected to a Spectrum ISP network.
Chrome and Safari report an error:
500 Failed to fetch dynamically imported module: https://cineversity.maxon.net/_nuxt/B_4WZ4t6.js
or
500
'application/octet-stream' is not a valid JavaScript MIME type.

Although Maxon support says it is on my end, 500 errors are on the server side.
After inspecting the site with Chrome Dev Tools,
The error message inside Chrome points to a Content Security Policy directive set to "script-src 'none'"

This causes the nuxt.js generated script (and subsequent scripts), CyjJQS-n.js, to not load and the site to fail to load on any browser which enforces CSP directives, such as Chrome or my Safari.
I believe it may be the CDN Maxon uses in my area, because if I change my geo location to Germany, the site opens fine.

I know this problem exists.
I know the issue is outside of my control.

If anyone can help, can you reach out?

I noticed a change to how the project files are shared. I get a message about logging into Dropbox. I created an account at Dropbox with the same email as my maxon account, but it still says I don't have access to the project files. How can I access project files? I am a part of the Maxon Teams Account Group. I have 32 licenses of Cineversity.

Thank you for your rapid reply. Your example file helped quite a bit. The use of reference materials was helpful. When I used it, I still had trouble with the fact that one material had a different projection than the other. This then reminded me of an older shader-graph method for showcasing stickers/decals/etc. I ended up using a UV Projection Node between the displacement texture and the Displacement node. Then I combined them in the Displacement Blender. While it doesn't appear to mix as easily as Color Layers do, the result did allow me to indent into the leather.
https://drive.google.com/file/d/118gFWWNXKMOW3_0CAiQxnxyHrZ_d2Bbp/view?usp=sharing
Thank you again.

Dr. Sassi,
I have been working through Elly Wade’s Tutorial on rendering Redshift Basketball. My intention is to add a team logo, and change the ball’s logo to Wilson to match our High School’s ball. My challenge is that I cannot properly stack the materials’ displacement when my logo is Projection-Flat and the Basketball’s displacement is UVW Mapping. It appears to do one or the other. I have tried to create a UVW from projection, but when I apply it to a Displacement Node, the surface textures become flat as well.

In my shared file, I have placed 2 duplicates of the same ball. The left one has proper UVW displacement in the leather (from the Basketball Material) but the Logo appears simply painted on, with no indentation. The one on the right, has displacement, so we can see the depth (displacement is in the right-most material "RS Wilson Logo Gold Trim"), but the general displacement of the leather is from a frontal projection. This is visible from above where there is the displacement stops.

How can I make the ball look like the example on the left for the leather, but have the impression/indentation like the basketball on the right?
File:
https://drive.google.com/file/d/11YosFlTy8D8539zshf4m-lxi_v6g9OXE/view?usp=sharing

@Dr-Sassi Thank you so much for you swift reply. I will investigate these suggestions. I am also pleased to see that the Maxon Developer's Cafe is a thing. I did not know there was such a thing. Thank you again. (Have you checked your drone for new firmware? My DJI Mavic 2 Pro supposedly has a new Remote ID firmware)

Is there a way to programmatically fill the string of text within the “Text Object (previously MoText)” Text Spline attribute. Specifically, I am needing to make a matrix object’s mograph selection ID(+1) to drive the string value found in the Text Spline attribute. I have created this with a single number in the Text Spline attribute, but can’t figure out how to programmatically change this value. In the end, I am trying to create a 20 sided die.

D20.c4d

I completely understand about the post. I am glad that you are able to take days off. I have been flooded teaching Drone flying this week, trying to get a unit in before our DJI drones here in the USA are grounded because of RemoteID.
I added a camera, but still had the same issue. I made a screen recording of the issue while using an RS Camera. Perhaps you could look one more time?
https://drive.google.com/file/d/1sAP0R4U9oREkVyyy4NvIWQklka0zUqUU/view?usp=drive_link

Thank you sir.

I was able to follow along with this tutorial until I wanted to cache and view the results.
I had a very odd problem when I cached the simulation. The cached files are about 20% the size (not file size, but viewport size) of the viewport when compared to the RS renderview. They were the same while not cached, but the moment after creating the cache, the RS renderview shows the exact simulation, but it is 1/5 the size.
Here are my project files:
https://drive.google.com/drive/folders/1vxDKDBvrmZrWDTuEtbY34Isncz3gl_oV?usp=sharing

Here is a screenshot of the difference RS Renderview/Viewport:
https://drive.google.com/file/d/1OU9thFDUGfLWfemVB-DfmpxekS4ZReHG/view?usp=drive_link

I am still not able to wrap my head around the vast visual changes to Pyro in C4D 2023.2.2. The pyro appears completely different, and I believe it has something to do with the changes to the Noise section in Pyro. I was able to alter some settings to begin to get the same wispy nature of Noseman, rather than the blockiness of the 2023.2.2 system.

Working on a Macbook Pro M1 Max 64, Ventura 13.5.

I posted this on the tutorial questions page, but got no response in 12 days. I assume it is because caching the render is not a part of the tutorial so I need to post in the QA forum.

I was able to follow along with this tutorial until I wanted to cache and view the results.
I had a very odd problem when I cached the simulation. The cached files are about 20% the size (not file size, but viewport size) of the viewport when compared to the RS renderview. They were the same while not cached, but the moment after creating the cache, the RS renderview shows the exact simulation, but it is 1/5 the size.
Here are my project files:
https://drive.google.com/drive/folders/1vxDKDBvrmZrWDTuEtbY34Isncz3gl_oV?usp=sharing

Here is a screenshot of the difference RS Renderview/Viewport:
https://drive.google.com/file/d/1OU9thFDUGfLWfemVB-DfmpxekS4ZReHG/view?usp=drive_link

I am still not able to wrap my head around the vast visual changes to Pyro in C4D 2023.2.2. The pyro appears completely different, and I believe it has something to do with the changes to the Noise section in Pyro. I was able to alter some settings to begin to get the same wispy nature of Noseman, rather than the blockiness of the 2023.2.2 system.

Working on a Macbook Pro M1 Max 64, Ventura 13.5.

@Dr-Sassi Thanks again for working through this problem. I want so much to expand our use of the Cineversity Tutorials in my program at school. I discussed with Tech support, and they said they were reporting the variations between older versions and the new versions as a bug to tackle. They appreciated the inclusion of a scene file and detailed descriptions. Pyro is the most exciting tool I have used in a quite a while.

I was able to get the 2023.2.1 working on one of the other Mac Studios in the lab. It is also running RS 3.5.15. I pulled in your example project. I really appreciate the help, but I still struggle to see that the explosion resembles the tutorial. The viscous and rippling nature of the tutorial's pyro (even at 2:30 in) is just so much more natural.
There is now a controllable Noise category which defines the shape of the emission's source. Previously this may have been handled (I assume) "under the hood" meaning that the noise was setup with some parameters by default. Can I set the new noise parameters to the previously (internal) settings so as to match behavior? Can I know what those settings were so as to not only recreate the previous behavior, but understand how the controls affect the system now?

Were you able to get the example file from Aaron?

Thanks for sending it over. I was waiting to upgrade to 2023.2.1, because I had gone through quite a bit to a get a 3rd party plugin, HOT4D to build and was worried it would break it. I will see if I can update an extra computer and check this out. Please allow me to respond again.

I couldn't upload a large enough file here, but there are no wispy tendrals, just boxes of fire and boxes of smoke.
These are both after the 2:30 mark, with no changes in the tutorial other than C4D version.