MeasureIt not updating mesh positioning after first render, Error in remapping process, and ensure_lookup_table bugs #52236

Closed
opened 2017-08-01 05:55:46 +02:00 by nBurn · 7 comments
Member

System Information
Windows 10, Intel HD 4600

Blender Version
Reproducible in both 2.78.5 e982ebd and 09eac01

Bug 1 - Fixed with 059aa14163

Short description of error

Mesh data is not changed after using the addon's built in render feature. After the first render, only changes to MeasureIt's open GL information will be captured in future renders (the mesh data stays the same).

Exact steps for others to reproduce the error

  • Make sure your scene has at least one mesh, light, and camera
  • Make sure the cameras focused on the mash
  • Enable the MeasureIt addon (if not already)
  • In the 3D View, open the toolbar and click on the display tab, and make sure the "MeasureIt Tools" option is expanded
  • Turn on measure it by clicking the show button in the toolbar panel
  • Add MeasureIt measurement labels or debug data to the mesh in the camera's focus
  • Make sure "Render type" in the "MeasureIt Render" sub panel in the toolbar is set to "*Current"
  • Click the "Render" button in the "MeasureIt Render" sub panel
  • Press Shift F to move the camera so it's viewing the mesh from a different angle
  • Click the "Render" button in the "MeasureIt Render" sub panel again to re-render the scene

Open the UV image editor and load the newly rendered image

3D View before second render
measureit_output_a.png

Second render output
measureit_output.png


Bug 2 - Fixed with 8068085bda

Short description of error

Somewhat related to Bug 1, after rendering an image with MeasureIt and pulling the rendered image up in the UV / Image Editor, if you go back into the 3D View and click MeasureIt's "Render" button a second time this error shows up in the console:

Error in remapping process from 'IMmeasureit_output' (000002733FA75228) to '' (0000000000000000): wrong user count in old ID after process (summing up to -1)

Exact steps for others to reproduce the error

  • Make sure your scene has at least one mesh, light, and camera
  • Make sure the cameras focused on the mash
  • Enable the MeasureIt addon (if not already)
  • In the 3D View, open the toolbar and click on the display tab, and make sure the "MeasureIt Tools" option is expanded
  • Turn on measure it by clicking the show button in the toolbar panel
  • Add MeasureIt measurement labels or debug data to the mesh in the camera's focus
  • Make sure "Render type" in the "MeasureIt Render" sub panel in the toolbar is set to "*Current"
  • Click the "Render" button in the "MeasureIt Render" sub panel
  • Open the UV image editor and load the newly rendered image
  • Go back to the "MeasureIt Render" sub panel in the "Display" tab on the 3D View's toolbar

Click the "Render" button in the "MeasureIt Render" sub panel again to re-render the scene

Bug 3 - Fixed with 69cb19cf71

Short description of error

Editing the mesh that is part of a calculate measured segments will throw an "ensure_lookup_table" error if the segments are part of a Sum group. Sample error message:

Traceback (most recent call last): File "measureit_main.py", line 415, in draw
p1 = get_point(obverts[ms.glpointa].co, myobj)
IndexError: BMElemSeq[index]: outdated internal index table, run ensure_lookup_table() first

**System Information** Windows 10, Intel HD 4600 **Blender Version** Reproducible in both 2.78.5 e982ebd and 09eac01 **Bug 1** - **Fixed with** 059aa14163 **Short description of error** Mesh data is not changed after using the addon's built in render feature. After the first render, only changes to MeasureIt's open GL information will be captured in future renders (the mesh data stays the same). **Exact steps for others to reproduce the error** - Make sure your scene has at least one mesh, light, and camera - Make sure the cameras focused on the mash - Enable the MeasureIt addon (if not already) - In the 3D View, open the toolbar and click on the display tab, and make sure the "MeasureIt Tools" option is expanded - Turn on measure it by clicking the show button in the toolbar panel - Add MeasureIt measurement labels or debug data to the mesh in the camera's focus - Make sure "Render type" in the "MeasureIt Render" sub panel in the toolbar is set to "*Current" - Click the "Render" button in the "MeasureIt Render" sub panel - Press Shift F to move the camera so it's viewing the mesh from a different angle - Click the "Render" button in the "MeasureIt Render" sub panel again to re-render the scene # Open the UV image editor and load the newly rendered image 3D View before second render ![measureit_output_a.png](https://archive.blender.org/developer/F688696/measureit_output_a.png) Second render output ![measureit_output.png](https://archive.blender.org/developer/F688693/measureit_output.png) --- **Bug 2** - **Fixed with** 8068085bda **Short description of error** Somewhat related to Bug 1, after rendering an image with MeasureIt and pulling the rendered image up in the UV / Image Editor, if you go back into the 3D View and click MeasureIt's "Render" button a second time this error shows up in the console: > Error in remapping process from 'IMmeasureit_output' (000002733FA75228) to '<NULL>' (0000000000000000): wrong user count in old ID after process (summing up to -1) **Exact steps for others to reproduce the error** - Make sure your scene has at least one mesh, light, and camera - Make sure the cameras focused on the mash - Enable the MeasureIt addon (if not already) - In the 3D View, open the toolbar and click on the display tab, and make sure the "MeasureIt Tools" option is expanded - Turn on measure it by clicking the show button in the toolbar panel - Add MeasureIt measurement labels or debug data to the mesh in the camera's focus - Make sure "Render type" in the "MeasureIt Render" sub panel in the toolbar is set to "*Current" - Click the "Render" button in the "MeasureIt Render" sub panel - Open the UV image editor and load the newly rendered image - Go back to the "MeasureIt Render" sub panel in the "Display" tab on the 3D View's toolbar # Click the "Render" button in the "MeasureIt Render" sub panel again to re-render the scene **Bug 3** - **Fixed with** 69cb19cf71 **Short description of error** Editing the mesh that is part of a calculate measured segments will throw an "ensure_lookup_table" error if the segments are part of a Sum group. Sample error message: > Traceback (most recent call last): File "measureit_main.py", line 415, in draw > p1 = get_point(obverts[ms.glpointa].co, myobj) > IndexError: BMElemSeq[index]: outdated internal index table, run ensure_lookup_table() first
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @nBurn

Added subscriber: @nBurn
Author
Member

Added subscribers: @BrendonMurphy, @VukGardasevic

Added subscribers: @BrendonMurphy, @VukGardasevic
Author
Member

lijenstina also reported the following two errors to the Blender Console when MeasureIt was being used, but I did not include the second in the task description as I have not yet figured out exactly what causing it to show up:

Error 1:

Error in remapping process from 'IMmeasureit_output' (000000000BA2D578) to '' (0000000000000000): wrong user count in old ID after process (summing up to -1)

Error 2:

Traceback (most recent call last):
File "measureit_main.py", line 415, in draw
p1 = get_point(obverts[ms.glpointa].co, myobj)
IndexError: BMElemSeq[index]: outdated internal index table, run ensure_lookup_table() first

lijenstina also reported the following two errors to the Blender Console when MeasureIt was being used, but I did not include the second in the task description as I have not yet figured out exactly what causing it to show up: Error 1: > Error in remapping process from 'IMmeasureit_output' (000000000BA2D578) to '<NULL>' (0000000000000000): wrong user count in old ID after process (summing up to -1) Error 2: > Traceback (most recent call last): > File "measureit_main.py", line 415, in draw > p1 = get_point(obverts[ms.glpointa].co, myobj) > IndexError: BMElemSeq[index]: outdated internal index table, run ensure_lookup_table() first
Antonio Vazquez was assigned by nBurn 2017-08-01 09:21:48 +02:00
Author
Member

@antoniov

I pushed a partial fix that should fix the Bug 1, but (if you can) could you please give this commit a quick look over (mainly the changes in measureit_main.py):
https://developer.blender.org/rBA059aa141639c93f075f2d75b5ff509d590a7219b

@antoniov I pushed a partial fix that should fix the Bug 1, but (if you can) could you please give this commit a quick look over (mainly the changes in measureit_main.py): https://developer.blender.org/rBA059aa141639c93f075f2d75b5ff509d590a7219b
nBurn changed title from MeasureIt not updating mesh positioning after first render to MeasureIt not updating mesh positioning after first render, Error in remapping process, and ensure_lookup_table bugs 2017-08-02 12:39:55 +02:00

This issue was referenced by 8068085bda

This issue was referenced by 8068085bda0192fff3bb28a27bdc3c269dd3bcef
Author
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
nBurn closed this issue 2017-08-11 19:48:41 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#52236
No description provided.