X14 Ray Trace quit on MacBook Pro


vivianyang2020
 Share

Recommended Posts

5 hours ago, vivianyang2020 said:

 

Is there anybody know the ray trace? My CA quit when I run the ray trace on my new MacBook Pro. I have no problem on 3D rendering, just can not run the ray trace. This is so frustrated!

Is there any way can fix it?

 

MacBook Pro whit M1 pro, 32/512.

So a couple of questions and a screen grab of the issue would help.  Just to confirm you are using the cpu ray trace tool correct?  Are you getting an image?  Do you see any information on the bottom status bar?

Link to comment
Share on other sites

1 hour ago, rgardner said:

So a couple of questions and a screen grab of the issue would help.  Just to confirm you are using the cpu ray trace tool correct?  Are you getting an image?  Do you see any information on the bottom status bar?

Thanks for your reply.

Unfortunately, there are no informations, and I didn't get image. I don't even have time to take a screenshot, the app just quit unexpectedly.

Link to comment
Share on other sites

9 hours ago, vivianyang2020 said:

Thanks for your reply.

Unfortunately, there are no informations, and I didn't get image. I don't even have time to take a screenshot, the app just quit unexpectedly.

And I am assuming after you restart your computer it happens every time?  To confirm you are using a CPU ray trace rendering correct?

Link to comment
Share on other sites

  • 5 months later...

I am having this exact same issue! @vivianyang2020did you ever figure out what was going on? @rgardner I restarted my computer and tried again and still the same thing. I click on the ray trace button to open the CPU Ray Trace Current View, click Ray Trace, and the program immediately quits. 

 

I am using a:

 

MacBook Pro (16-inch, 2021)

Chip Apple M1 Max

Memory 32 GB

 

I am on CAx14

Screen grab.png

Link to comment
Share on other sites

2 hours ago, Ikra2020 said:

I am having this exact same issue! @vivianyang2020did you ever figure out what was going on? @rgardner I restarted my computer and tried again and still the same thing. I click on the ray trace button to open the CPU Ray Trace Current View, click Ray Trace, and the program immediately quits. 

 

I am using a:

 

MacBook Pro (16-inch, 2021)

Chip Apple M1 Max

Memory 32 GB

 

I am on CAx14

Screen grab.png

Does it do it with another file?

Link to comment
Share on other sites

Have had crashes as well. Turning off the lights has helped alleviate the problem.  

 

I don't make many interior views so this has been reasonably acceptable.  But for those who do interiors, this crashing issue will hopefully be looked into. 

 

If you note on the Forum, you'll see many people with Apple products (M1 chip) discussing TwinMotion in recent months. It's a viable alternative for rendering.

 

The problem is however... RayTrace type of renders are unsupported in TM. But there is excellent refraction quality on glass and metallic surfaces, and the results can often be quite good.  

 

Sorry that this is not a help. If anything it merely confirms that you are not alone in your findings. CA techies review the forums and may be keenly aware. Keep the faith that a new release is coming, and perhaps in due time this crashing issue is going to be addressed. 

Link to comment
Share on other sites

@VHamptonappreciate your response--it certainly helps to know I am not alone! 

 

It is very strange though because I did a ray trace about week ago with no issues so I don't understand why this is happening all of a sudden :(

Link to comment
Share on other sites

You're quite welcome.

 

In having explored every possibility on one project, I discovered that the culprits were a couple of garage sconces.  After they got deleted from the plan file... Presto. Ray Tracing was possible again.

 

Could it be that one or more items were introduced to you project in recent days? It seems that lighting is the Achilles heel to the M1 chip - not just w/ Chief Architect, but other software makers as well.

 

I've been doing extensive research, and despite the hype of Apple's chip (which is an extremely fast and hearty work horse) it does have a couple of quirks to be worked out. Not any fault of the software developers. 

 

Intel chips have always been the industry standard. The M1 is new, and cut from a different cloth so to speak. 

Link to comment
Share on other sites

Hi There,

Didn't think the Macbook pro could do a raytrace. Have just ordered a new Macbook pro 16" with M2 chip and wasn't expecting it to raytrace.  Other Macbook pro users out there.. am I correct? or can you raytrace..

 

Link to comment
Share on other sites

While I don't have a MacBook, M1 chips can RayTrace as do the newer M2 chips. Obviously there are still issues here and there. 

 

Again, many software developers are making their very best efforts to accommodate the hardware changes. Having said that, I was a Windows user for many many years, and the very best computers (for rendering) are typically Windows systems with the magic Nvidia card. Gaming computers in particular.

 

CA has always been extremely loyal to its user base and it wasn't until something like 8 year ago that one could even use CA on an Apple product. They will come through. The folks in the tech department are continuously making improvements on the software. X-15 may possibly result in some welcome upgrades.  

Link to comment
Share on other sites

@VHamptonthank you for the insight--I think you might be right--it must be some component I've added to the plan that is messing it up! I just started a new plan and drew a basic box with four walls, a door, and 2 windows and PRESTO, raytrace began! Now to figure out what is causing the issue in my other two plans.... (I have downloaded a few models from the SketchUp 3D warehouse so I'm guessing it might be one of those?)

Link to comment
Share on other sites

You're very welcome... and yes, always be careful with the 3D warehouse. They have incredibly helpful things on the site, but any objects over the 2-3MB range should be used sparingly. 

 

Example... they have some awesome cars and trees on the site, but objects w/ over 12megs of data means that they've got many many surface layers. That can bog a plan down quickly. Stick with low-poly objects whenever possible, and the plan file will remain fast and smooth - as it should.  By way of example, pretty much all of the Chief Architect 3D library inventory is on the lower end of the surface count spectrum. 

 

Regarding a way to track down where things went side-ways, try opening the manage archives folder.

 

Top left under Find. Choose one of your past files (Manage Auto Archives) going back to the approximate date of when the program started acting up, and then give the RayTrace process a go. You may be able to sleuth your way through the steps in what may have been introduced or changed before things went haywire. In the camera view delete or turn off various objects to see which ones may or may not cause the crash. Since the file is archived, there's never that uneasy concern as if you were taking apart the original. 

 

Good luck with that! ...It's great to know that you can RayTrace again. 

 

...as any FYI, when you have a moment place your system specs. and current version of CA in the signature if you have time.  In the eventuality that users may have to pay a visit in the future, having info. on system spec.s can help folks who may be trying to help. Not that it's needed here, but the forum police hand out warnings on occasion. Lol All the best.  

Link to comment
Share on other sites

In X14, if you are crashing using the CPU Ray Trace on an M1 machine, you can right click on Chief Architect Premier X14 in Finder under Applications and select Get Info. A window will pop and there should be a checkbox that says "Open using Rosetta". Check that checkbox and that should allow you to use CPU Ray Trace.

 

 

279825989_Screenshot2023-01-25at2_29_48PM.thumb.png.20093597e3a71a9cbbef36fc7db0ecad.png

  • Upvote 2
Link to comment
Share on other sites

Glad to be of help Kyra... and thank you Steven.

 

Rosetta options sometimes pop up immediately when using a certain software. Many may not be aware that this box needed to be checked with Chief Architect.

 

In case folks from the future may want to learn more, this link from Apple is somewhat enlightening: https://support.apple.com/en-us/HT211861

 

All the best - Val

Link to comment
Share on other sites

On 1/25/2023 at 12:01 PM, Arcadian said:

Hi There,

Didn't think the Macbook pro could do a raytrace. Have just ordered a new Macbook pro 16" with M2 chip and wasn't expecting it to raytrace.  Other Macbook pro users out there.. am I correct? or can you raytrace..

 

Although our MacBooks can ray trace it is CPU ray tracing. Real time ray racing will not work on a Mac. 

Link to comment
Share on other sites

  • 2 months later...
On 1/25/2023 at 5:33 PM, StevenK said:

In X14, if you are crashing using the CPU Ray Trace on an M1 machine, you can right click on Chief Architect Premier X14 in Finder under Applications and select Get Info. A window will pop and there should be a checkbox that says "Open using Rosetta". Check that checkbox and that should allow you to use CPU Ray Trace.

 

 

279825989_Screenshot2023-01-25at2_29_48PM.thumb.png.20093597e3a71a9cbbef36fc7db0ecad.png

 

This helped after I did a reboot! 

Thanks so much! 

  • Upvote 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

  • Member Statistics

    33800
    Total Members
    9156
    Most Online
    Danders
    Newest Member
    Danders
    Joined
  • Similar Content

    • By AlamoChief
      I just bought a new LG 32" 4K monitor and found my PBR render speed was slower than on my 27 Inch monitor. I discovered that the size of the window affects the render and denoise speed. With the window size the same on each monitor the speed is equal. If I shrink the window size to about 8" of render display the time to render and denoise is almost instantaneous. If I have the window full size on the 32" display the time goes up to about 9 seconds to finish rendering and denoise. I now know that if I'm just looking around to see what the model looks like a smaller window will speed up the process greatly. I hope this helps to understand how the render speed works. 
    • By 3919395k
      Hi,
      I have been using X12 since it came out and for some reason, I am forever struggling with achieving some of those beautiful renderings I've seen others post.  I have looked through this forum for clues, and while I have found some great pointers, I still come up with lousy renderings.  I have notes from threads I have gotten here about settings, and making sure you have a slab and roof, etc...but still I find myself struggling with this.  My biggest frustration is with lighting.  How does reduce the sunlight that comes in through the windows?  Then its the light that you see come through the mirror, sofa, ceiling.  This rendering was done in about 30 passes+ which I've read shouldn't take this long to produce if your width and height is adjusted to read 800(?) Any advice would be greatly appreciated.
       
      Thank you~

    • By Tkangas
      I am very perplexed by the lack of light in the interior physically based ray tracing camera. They always appear to be taken with all the interior lights off. 
      What I have tried so far:
      - adjusting the camera exposure and brightness
      - adding lights and light sources
      - increasing the maximum number of lights on
      - adjusting the sun angle, etc.
       
      I can NOT figure out how to make the interior rooms brighter!! I would LOVE if someone can help! This is a very powerful tool if it can be rendered correctly
       
      both attached images have light sources that are turned on
       
       
       


    • By Designer_Maddee
      I have been trying to create more photorealistic renderings with Chief as I don't have the current budget for additional software. 
      I have been playing with the CPU Ray Trace option and keep coming up with grainy images that seem darker than I'd like.
      I have played with the lighting and sunlight and I've pushed the resolution higher and higher every time I try with no luck. 
      If adjust the contrast of the image it makes it a little brighter, but it still is lacking. 
      The first image went for 60 passes, the next one was 40 and the 3rd was 50 passes. 
      I would love some insight and recommendations on fixing the grainy look as well as just creating more realistic images!
       
      Thank you!
       
      I am using Premier X13 on iMac
       



    • By Renerabbitt
      X-13 RTRT, A breakdown from another forum in response to growing frustrations with RTRT.  (Items that are specific and searchable terms in CA have capitalized first letters)   There is nothing "wrong" with the new Astral PBR RTRT option. Better understanding of a modern rendering engine may help alleviate some issues. If you are feeling overwhelmed by this info you can always uncheck the option for the RTRT in your Rendering Techniques Tool. Feel free to contact me for support or advanced training. • In RTRT a low sample rate is used in live camera views. • For exported presentations images similar to a CPU-based RT, set your Maximum Export Samples as low as needed to eliminate fireflies and light leaks. The higher the sample rate in RTRT Rendering Techniques, the better the image(up to a point where benefits are negligible). This only applies to the Export Image Tool. • A sample rate in basic terms is the number of samples from a camera of a given Objects Material ID as it applies to the geometry of an object, including colors, lighting, shadows etc. The more times something is sampled the less aliasing there exists in a final image. • The more light exists in the scene the easier it is to Sample. • You must supply ample light in adjacent rooms for the RTRT engine to properly process and "trace" your scene. Devoid of light, your exterior will be overly exposed, your interior may be underexposed, and you may have fireflies or light leaks. • Ensure that your active Light Set is on and illuminating your scene, which is accessed a number of ways, one being the Edit Active View tool, in the Camera Panel, under the Lighting Section. • With ample lights, an interior scene Rendering Technique Options might have an exposure from .15-.35, a Maximum Sample Rate of 500-1500, a Brightness between -10 to 0, a Backdrop intensity between 100-1000. This is not and never will be a universal setting, each scene needs adjustment according to the amount of light available to that scene. • If your scene is underexposed you may need to adjust your lighting including the lumens of your light fixtures. • Sun settings will do very little to help overexposure, underexposure, light leaks or any other trace related problems. This is the nature of a tracing engine. • Live view will always be of lesser quality than an exported image using the Export Tool(because of the option to change the sample rate.) • Typical problem causing issues: Caustics, Lights near transparent or translucent surfaces, lights of high Lumen values in one room juxtapose to lights of low lumens in an adjacent room. High resolution bump/roughness/normals maps in materials. These issues all cause difficult scenarios for attenuation and aliasing.    Some of the fixtures being used are not optimized for this new engine. Consider changing the material properties of any glass that is in close proximity to a light source. Changing the glass material of a light fixture that is turned on in a RTRT camera from Transparent class to General Material with high Transparency can yield much more predictable results. Same goes for situations when inside cabinet lights do not show up in RTRT behind Transparent Class windowed cabinet doors.   There is a lot more to this, you can have some success with this info, but barely scratches the surface. For some incredibly good generalized rendering info, read the Thea Render Manual(free online) It has some fantastic info in it that applies to all rendering engines. The following images are a RTRT with zero lights(screen clipped), an RTRT with lots of lights and same settings(screen clipped), and an RTRT export of the same scene The last image has the backdrop turned up since the sun direction is not illuminating the backdrop. Backdrop setting of 1000.