Itoo Software Forum

Author Topic: First Marker not read before first segment?  (Read 156 times)

Alex.S

  • Full Member
  • ***
  • Posts: 108
First Marker not read before first segment?
« on: January 29, 2020, 06:28:29 PM »
Here's a super simple scene, just switching two nodes, based on the first user data. But it seems the first object is always generated before reading the first marker? Even when it's set right at the start of the spline?

Is this a bug or am I missing something obvious?


Dragan

  • Sr. Member
  • ****
  • Posts: 433
Re: First Marker not read before first segment?
« Reply #1 on: January 29, 2020, 06:46:59 PM »
Hi.
Attach so-called `NULL` segment to the Marker connector. (optional you can attach Selector node)
« Last Edit: January 29, 2020, 06:50:29 PM by Dragan »

Alex.S

  • Full Member
  • ***
  • Posts: 108
Re: First Marker not read before first segment?
« Reply #2 on: January 29, 2020, 06:48:47 PM »
Great that's easy enough. Thanks!

Alex.S

  • Full Member
  • ***
  • Posts: 108
Re: First Marker not read before first segment?
« Reply #3 on: January 30, 2020, 12:51:13 PM »
The trouble is now I get overlapping geo.

I tried putting a null segment into the start piece, but that doesn't effect it either.

I can manually set the point so it doesn't overlap, but that's not really desired, especially if i want to make something continuous.
« Last Edit: January 30, 2020, 12:52:58 PM by Alex.S »

Alex.S

  • Full Member
  • ***
  • Posts: 108
Re: First Marker not read before first segment?
« Reply #4 on: January 30, 2020, 01:34:39 PM »
If I add a fixed size of 0.01 to a null start segment and nothing in the marker point, it seems to not generate overlapping objects. But what if I want to use the start piece for something, but modify it with data from the Markers? Seems like a bug to me?

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2282
    • iToo
Re: First Marker not read before first segment?
« Reply #5 on: January 30, 2020, 03:08:17 PM »
Thanks for Your help. We have fixed few issues regarding Markers.

  • MarkerData for Default segments is not computed correctly when Marker is set at 0.0. Moving it to 0.001 fixes it. This was a bug.
  • Selector operator behaviors incorrectly when Index is connected to an expression returning 0.0.

Note:
Remember that Selector index starts at 1. The default value for XMarkerData is zero, and that can be confusing when using the Selector node.
Rokas
iToo Software

Alex.S

  • Full Member
  • ***
  • Posts: 108
Re: First Marker not read before first segment?
« Reply #6 on: January 30, 2020, 05:10:12 PM »
Yeah I've been configure the marker data to reference a default parameter, which is used when 0 is returned from the marker data.

Good to hear the first thing has been fixed.