[loading problem]Unable to run a simulation
-
[loading problem] anyone familiar with sketchy physics who can help me? whenever i try to run a simulation i get this error code.
-
That exact error is mentioned in other threads here http://forums.sketchucation.com/viewtopic.php?f=61&t=31262&start=45 and here http://www.sketchucation.com/forums/viewtopic.php?f=61&t=33128
It seems to be related to SP running on Mac OS earlier than X 10.6. Are you running SP on a Mac and if so what OS?
Also, if you have a lot of Sketchup plugins there might be a conflict, so it might be worth trying moving them all to a temporary folder and see if that cures the problem and then put the plugins back into the original plugin folder one by one to pinpoint where the conflict is. However that is a long shot and a lot of work, so the best thing might be to re-install SP 3.2 as that sometimes seems to fix problems.
Also, if you open Ruby Console from the Window menu of Sketchup and copy ans paste the text that appears when you run the model, it might help the real experts here tell you what is wrong.
Finally, this might work:
Find the ControllerCommands.rb file using the path shown in the error message and open it up in a text editor. Put a hash (#) in front of the line that contains "@sounds=SPSounds.new()" at around line 777 half way through the file and save the file. This will prevent any models that use sound from working, but on my PC it will allow models that do not use sound to work normally. This is just a temporary workaround fix until someone that really knows what they are doing, like CPhillips provides a proper fix. If that does not work, remove the hash you added and re-save ControllerCommands.rb to put everything back as it was.
Let me know if any of that works.
-
Hey Kev,
First let me start off by thanking you for the detailed answer. It really gave me a handle on how to attack this problem. I really appreciate all the detailed research. I'm running SKP7.1 on win7X64. I tried the hash in the ControllerCommands.rb which unfortunately did nothing. With your help i tracked it down to some old plugins that were clashing. It was time for some spring cleaning. Cheers mate.
Advertisement