First time here? Check out the Help page!
1 | initial version |
It is possible that Windows 8 introduced a bug in our ability to directly launch a model in the stand alone OpenStudio application from SetkchUp, but try doing this.
Let me know if that doesn't work for you. If it doesn't work confirm if it doesn't work with any OSM, or just one in particular that you are working with. Then we can see if it is an issue with the OSM file or Windows 8.
To follow up on launching the OpenStudio application from within the SketchUp Plugin, we didn't test 1.4 with Windows 8, but we did test Windows 8 with OpenStudio 1.5. Note that to upgrade to OpenStudio 1.5.0 would also require you to install SketchUp 2014. If you still see the error here, then maybe there is a file permissions issue?
2 | No.2 Revision |
It is possible that Windows 8 introduced a bug in our ability to directly launch a model in the stand alone OpenStudio application from SetkchUp, but try doing this.
Let me know if that doesn't work for you. If it doesn't work confirm if it doesn't work with any OSM, or just one in particular that you are working with. Then we can see if it is an issue with the OSM file or Windows 8.
To follow up on launching the OpenStudio application from within the SketchUp Plugin, we didn't test 1.4 with Windows 8, but we did test Windows 8 with OpenStudio 1.5. Note that to upgrade to OpenStudio 1.5.0 would also require you to install SketchUp 2014. If you still see the error here, then maybe there is a file permissions issue?issue? Below are steps to work around this using your current installation.
Using 1.4.0 try try the following steps. 1. Save the OSM in the SketchUp plugin using the "Save OpenStudio Model" button or menu item. 2. Launch the Stand alone OpenStudio application from your start menu (or some other way, other than from the SketchUp plugin button) 3. Load your OSM by using the "file" menu in the stand alone OpenStudio application.
Let me know if that doesn't work for you. If it doesn't work confirm if it doesn't work with any OSM, or just one in particular that you are working with. Then we can see if it is an issue with the OSM file or something else.