PDA

View Full Version : Can someone confirm a bug for me? 1-2-3 PFX crash



Scazzino
01-30-2018, 10:42 AM
Hi can someone confirm a bug for me? I want to make sure it's not just my setup before I report it and see if it's Mac only (I'm on El Capitan) or across the board. I'm currently testing a Discovery version of LW2018 so I can't save a scene, but it's so simple you don't need to save anything.

Try this in Layout 2018.0.1

1) Add a Null
2) 'p' to open Object properties and add an FX_Emitter
3) Set the emitter Nozzle to Object-Vertices and hit Calculate

Here Layout immediately crashes. Same thing happens in 2015.3 which crashes both Layout and the Hub.

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.newtek.LightWave.ParticleFX 0x000000011a13a8c4 0x11a0e8000 + 338116
1 com.newtek.LightWave.ParticleFX 0x000000011a0f69aa 0x11a0e8000 + 59818
2 com.newtek.LightWave.ParticleFX 0x000000011a0f7992 0x11a0e8000 + 63890
3 com.newtek.LightWave.ParticleFX 0x000000011a0f94f3 0x11a0e8000 + 70899
4 com.newtek.LightWave.ParticleFX 0x000000011a0fa96c 0x11a0e8000 + 76140
5 com.newtek.LightWave.ParticleFX 0x000000011a110102 0x11a0e8000 + 164098
6 com.newtek.LightWave.ParticleFX 0x000000011a110cf5 0x11a0e8000 + 167157
7 libtools.2018.0.1.dylib 0x000000010c289c7e 0x10c15e000 + 1227902
8 com.newtek.LightWave.Layout 0x000000010bb68222 0x10bada000 + 582178
9 libtools.2018.0.1.dylib 0x000000010c18ecd1 ActionDefDispatch + 145
10 libtools.2018.0.1.dylib 0x000000010c1b05f1 CmdEntryFireTag + 193
11 com.newtek.LightWave.Layout 0x000000010bb245d4 0x10bada000 + 304596
12 com.newtek.LightWave.Layout 0x000000010bbcbab9 0x10bada000 + 989881
13 libtools.2018.0.1.dylib 0x000000010c1bd2bf 0x10c15e000 + 389823
14 libtools.2018.0.1.dylib 0x000000010c1bd756 0x10c15e000 + 390998
15 com.apple.AppKit 0x00007fff9cc553c9 -[NSWindow _handleMouseDownEvent:isDelayedEvent:] + 6322
16 com.apple.AppKit 0x00007fff9cc563ad -[NSWindow _reallySendEvent:isDelayedEvent:] + 212
17 com.apple.AppKit 0x00007fff9c695539 -[NSWindow sendEvent:] + 517
18 com.apple.AppKit 0x00007fff9c615a38 -[NSApplication sendEvent:] + 2540
19 libqcocoa.dylib 0x0000000119ca4c7e -[QNSApplication sendEvent:] + 78
20 libqcocoa.dylib 0x0000000119ca1257 QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1351
21 libtools.2018.0.1.dylib 0x000000010c17bb29 0x10c15e000 + 121641
22 libtools.2018.0.1.dylib 0x000000010c2c720a WManGetInput + 442
23 com.newtek.LightWave.Layout 0x000000010bc0f889 0x10bada000 + 1267849
24 com.newtek.LightWave.Layout 0x000000010bcb6bed 0x10bada000 + 1952749
25 com.newtek.LightWave.Layout 0x000000010bae6f44 0x10bada000 + 53060

prometheus
01-30-2018, 11:33 AM
It crashes here too, the thing is, it shouldnīt crash, it should however give you an error message saying..there are no vertices to calculate.
After all...what to expect? you added a particle emitter to a null object, which has no points/vertices..so when calculating it looks for something that isnīt there..CRASH BOOM BANG.

Verify, add a box, p- for properties and add particle emitter fx on that, change nozzlel to vertices.. and calculate and see what happens.

fishhead
01-30-2018, 11:46 AM
Crashes here also (Win7, 2018.0.1) - Tried a (layout created) CubeObject which worked fine...

Sensei
01-30-2018, 11:46 AM
Confirmed on LW 2018.0.1, and bug reported..

Scazzino
01-30-2018, 12:04 PM
Thanks for the confirmations. I reported it.

Of course you wouldn't normally set an emitter to object vertices on a null (because there are none) but it shouldn't crash Layout. It would be nice if it generated particles from the pivot of the null. That's what I was trying to see if it would do (so I wouldn't have to create a one point object) but it crashed instead. What I really expected it to do was nothing, because there are no points. I certainly didn't expect it to crash both Layout and the Hub. That should never happen regardless of user input or it means some special case input has not been checked/trapped for errors.

prometheus
01-30-2018, 12:45 PM
Thanks for the confirmations. I reported it.

Of course you wouldn't normally set an emitter to object vertices on a null (because there are none) but it shouldn't crash Layout. It would be nice if it generated particles from the pivot of the null. That's what I was trying to see if it would do (so I wouldn't have to create a one point object) but it crashed instead. What I really expected it to do was nothing, because there are no points. I certainly didn't expect it to crash both Layout and the Hub. That should never happen regardless of user input or it means some special case input has not been checked/trapped for errors.

Absolutely, it shouldnīt crash, and error message just saying not valid or something would be nice.

for generating from the pivot, just add a particle emitter and scale down emitter size to zero, for it to start emitting out as in normal directions, you need a little vibration, perhaps combined with explosion, but only explosion do not work, you could also just set some velocity m/s in one of the x-y-z coordinates, but scaling it down to zero allows for it to emitt from a pivot point.

Scazzino
01-30-2018, 12:56 PM
Here's another crash.

1) Add a null, press 'p', fx tab and add an emitter
2) Click the calculate button twice (not a double-click).
3) Switch to the Primitive tab before the calculation finishes.

Here layout crashes when the calculation finishes.

I reported it, but let me know if it also happens for you guys too anyway.

Scazzino
01-30-2018, 12:59 PM
Absolutely, it shouldnīt crash, and error message just saying not valid or something would be nice.

for generating from the pivot, just add a particle emitter and scale down emitter size to zero, for it to start emitting out as in normal directions, you need a little vibration, perhaps combined with explosion, but only explosion do not work, you could also just set some velocity m/s in one of the x-y-z coordinates, but scaling it down to zero allows for it to emitt from a pivot point.

Yes, you could do that. I just create a one point object and use that. It would be nice to have an option for pivot point in the emitter though.

bazsa73
01-30-2018, 01:03 PM
Had this same issue. Reported 2 weeks ago.

Scazzino
01-30-2018, 01:06 PM
BTW: The calculate button should only permit one calculation (canceling any previous calc in progress). Currently you can hit it many times and it spawns many calcs with windows all stacked on top of each other, and then crashes when done. Looks like you don't even need to switch tabs to trigger the crash. The reason I was switching tabs was because I was trying to reproduce another bug where the fx_emitter was showing in the geometry tab (primitive tab in 2018) custom object list rather than just the fx tab list as it should. It happened to me when I was working and then crashed so I was trying to see how it got that way. It was like that tab was showing the wrong list or something.

- - - Updated - - -


Had this same issue. Reported 2 weeks ago.

Which issue? The null calculate crash, or the multiple click calculate button crash?