Can't raytrace anymore X1!

[Tommy Blair]

As of 30 minutes ago, I can't raytrace anymore in X1!!! I now get this notice. I can still raytrace in V10. I reloaded the program from the X1 CD and still can't rayrace. I was raytracing yesterday in X1 just fine! Any ideas??

[ChiefChris]

I got that once too...

I think it was when I went back into 10 a did a raytrace in 10....

silly question but...what did you do when that message came up?

If I remember...I just clicked yes...and it ran OK.

[Tommy Blair]

I had an untitled plan. Put a tv in a blank room. Tried to raytrace. I did click yes. It should have come up quickly. I switch from 10 to X1 all the time? Never had this happen before. I did the same scenario in V10 and the raytrace was quick...no messages.

[ChiefChris]

I had it one time...and I think (if I remember correctly) it was when I opened 10 after having X1 runing for some time...and I tried raytraced in 10..then went back to x1 later....I'm not sure though.

but, I am sure that I just clicked yes....

I cant recall anything else that I may have done. But, I haven't had trouble since.

[Tommy Blair]

Let me ask this. If I reload CA X1 without deleting it, will I lose custom plan templates, symbols, cad details, all my custom textures, etc?? I've never tried that.

[ChiefChris]

I wouldn't think so...but you might want to back them up just in case.

Just copy them to another folder on your HD...in my documents....

[ebdesign]

Tommy,
I believe that all your custom stuff you've collected for vX1 is in the "vX1 My Data Folder". Wherever you have that, make a copy of it you should be "good to go". Might want to browse through that folder just to make sure. I was looking through mine, & everything seems to be there, including "My CAD blocks" & "My moldings". You can always make copies of everything & then replace the default Chief stuff after you've reloaded. Makes you nervous though, eh?
Jim

[Tommy Blair]

I'm trying the "repair" from the CD. I made a copy of the data folder.

[Tommy Blair]

Well, I'd like to thank Dan Park for working with me on this problem this afternoon. We didn't get it fixed but fixed the original error message but then got another one that Dan wasn't familiar with. Given enough time...probably many hours, we might have been able to find the problem. Instead, we decided to just remove X1 completely an do a fresh install. That did it and all is fine now. I've been running Chief extensively for years and never ran into this problem. Anyway, it's history now.

Thank you for your time Dan.

[ChiefChris]

now that you mentioned it....that's what I did too. it happened when i did work in 10, then went back to x1..raytracing work that is....it's all coming back to me now.

sorry i couldn't have been much more help. it happened once a while ago, and I just couldn't remember....

[cjprowant]

Tommy,

I ran into this exact problem over the weekend. At first, I clicked yes on the message to continue with the raytrace. My computer froze. In the end, I went to chiefarchitect.com and reinstalled the most recent update of x1. I was already running the most recent update, but reinstalling it worked for me. I am not sure why I had this issue, so if Dan or anyone else knows why, that would be helpful. I do not want to have to go throught it again. I have run 4 full raytraces since then with no errors.

Carl

[Tommy Blair]

Good to know. Maybe Dan will see this post.

[Dan Park]

I worked with Tommy for quite a while on this one.

It's clear that doing a clean reinstall solves the problem so it's likely a file issue. That narrows it down but it's a big search space. We tried removing just the POV folder and reinstalling but that didn't fix the problem but it gave us a different result.

At this point it's hard to say what causes the problem. I think it's a corrupt file but I can't be totally sure what is going on here. The more of these cases we work in tech the more likely we are to have a solution but they are extremely uncommon so we don't have much experience with them.

I suspect based on querying the support team that we have had perhaps 3 calls on this error in X1 and the fixes seem to be all over the board.

One fix seems to be reinstalling the latest update, One fix is to ignore the message, and the last one is to do a clean reinstall.

[cjprowant]

Dan,

Thanks for the response. If I have an issue again, I will send the file to support.

Carl