RangeError 0x000107f0f05390 is not id value

lukanuts
243 ●1 ●6

Avi
4320 ●2 ●11

Dear all I have been facing this error on Euclid for Sketchup. You can test the attached file.

ERROR:
RangeError
0x000107f0f05390 is not id value

BACKTRACE:
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/sketchup/Sketchup.rb:101:in `_id2ref'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/sketchup/Sketchup.rb:101:in `drawing_interface'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/interfaces/Zone.rb:136:in `block in update_entity'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/interfaces/Zone.rb:135:in `each'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/interfaces/Zone.rb:135:in `update_entity'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/interfaces/DrawingInterface.rb:80:in `draw_entity'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/interfaces/ModelInterface.rb:204:in `block in update_model'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/interfaces/ModelInterface.rb:200:in `each'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/interfaces/ModelInterface.rb:200:in `each_with_index'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/interfaces/ModelInterface.rb:200:in `update_model'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/interfaces/ModelInterface.rb:117:in `draw_model'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/ModelManager.rb:182:in `open_input_file'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/ModelManager.rb:65:in `attach_input_file'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/ModelManager.rb:57:in `start'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/PluginManager.rb:141:in `new_model'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/PluginManager.rb:65:in `start'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/PluginManager.rb:218:in `<module:LegacyOpenStudio>'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/lib/legacy_openstudio/lib/PluginManager.rb:23:in `<top (required)>'
C:/Program Files/SketchUp/SKETCH~2/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb:54:in `require'
C:/Program Files/SketchUp/SKETCH~2/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb:54:in `require'
C:/Users/luca/AppData/Roaming/SketchUp/SketchUp 2017/SketchUp/Plugins/euclid/startup.rb:37:in `block in <top (required)>'
SketchUp:1:in `call'

CONFIGURATION: Euclid 0.9.3 SketchUp 17.2.2555 64-bit Pro Ruby 2.2.4 x64-mingw32

Any suggestions would be appreciated.

Regards Luca

add a comment

answered 7 years ago

Peter Ellis

1059 ●5 ●15 https://bigladdersoftware.com/

This error is reported by users after saving their model using the SketchUp File/Save menu command (which saves the .skp file, but also triggers the .idf file to be saved), and then attempting to reopen the .skp file with the SketchUp File/Open command.

The correct process is to NOT USE the SketchUp Save and Open commands. Instead, use the Euclid menu options to save and open the EnergyPlus .idf file. Save the EnergyPlus file using the menu command Extensions/Euclid/Save. Open the EnergyPlus file using the menu command Extensions/Euclid/Open...

This is a common problem that many new users run into. We've documented it in our issue tracker as a bug and hope to find a more user-friendly way to anticipate the mistake.