Bug: 1.0.51 light_point entities cannot be edited

#1 Same problem...

#2 Hmm - I'm not seeing this. If I put together a full package with all exe's and DSO's, can you DL it to see if it solves the issue? Maybe I missed updating some DSO somewhere...

#3 I'd be happy to. Feel free to contact me as needed.

#4 For those who are having this trouble, you can open the .CSX file manually in a text editor and set the values manually.

Look for:

<Entity id="1" classname="light_point" gametype="Constructor" isPointEntity="1" origin="0 0 30.5" direction="0 -0 -0">
<Properties color="255 255 255" intensity="100.0" falloff_inner="1.0" falloff_outer="10.0" />
</Entity>

#5 Should we maybe backtrack to a previous version that didn't have this?

#6 Ah! A quick clarification on the bug.

You *can* edit the lights through the Manage Entities dialog. It's the Properties panel that will not accept input on entities.

Scene menu -> Manage Entities is much easier than manually editing the CSX. =)

#7 Is this issue going to be resolved soon?

#8 I'll try to put up a full download this weekend. I'll even make an effort to check in all the code, and get a real build going. Sorry for the delays, it's been extremely stressful at work the past few weeks.

#9 Thanks Jaimi, we appreciate your hard work!

#10 A full download?! That would be great ^^

#11 @John, Benjamin -

I have sent you a link via email to your public email addresses. Please let me know if this solves the problems with editing of entities.

Jaimi

#12 I tried quickly, and the issue is resolved \o/

What's strange, is that it seems to have resolved the issue even for my older Ctor install directory oO

#13 Sorry Jaimi, the problem remains.

To reproduce on my system:

Start Constructor.
Click "Add Point Entity" button on Tools panel.
Place it, click Make to finalize.
In Properties panel, Object tab, try to enter falloff_inner or falloff_outer values. Default values of 1.0 and 10.0 cannot be deleted, overwritten, or modified.

Let me know if there's anything else I can do to help track down the problem!

-- John

#14 @John - I was able to duplicate this on my x64 machine this morning. It's some sort of timing problem. I'll try to track it down tonight.

#15 Update:

I believe I have fixed this. The problem is bizarre, but it appears that some function is rounding u32 values off to a multiple of 32 internally. But... not always (only on assignment or printing, not on evaluation!). If you'll look at the console, you can see the error being generated when you get the bad behavior:


!!! EntityPropertiesForm::processTick(): Diff entity time 258859656 vs 258859656


To me, those look the same. At some point, the engine decides they are not, they are off by 8. I can get past the error by rearranging the logic slightly. I will do so, and post the update soon.

#16 Yikes, that's an odd one... Good hunting!

#17 @John - I emailed you an updated dso that should solve the problem. I can only get this to duplicate on my 64bit XP box, which I don't have at home, but I think this should do it. Just replace the same dso you already have with the one in the mail.

#18 Awesome, Jaimi, that did the trick! Woot!

#19 Worked for me too - thanks Jaimi. Perhaps put it in a point release?

#20 Yeah - I have another bug I would like to fix with texturing, once I have that done, I'll put up another point release.