Talk:What's Changed With Havok4 - Revision history

Dale Innis: New section: Known bugs

2008-04-22T04:21:01Z

← Older revision		Revision as of 21:21, 21 April 2008
Line 19:		Line 19:

	[[User:Argent Stonecutter\|Argent Stonecutter]] 16:57, 31 March 2008 (PDT)		[[User:Argent Stonecutter\|Argent Stonecutter]] 16:57, 31 March 2008 (PDT)

			== Known bugs ==

			The things in Known Bugs have presumably been fixed now? They wouldn't have rolled out H4 with collisions and volumedetect not working...

Argent Stonecutter at 23:57, 31 March 2008

2008-03-31T23:57:57Z

← Older revision		Revision as of 16:57, 31 March 2008
Line 10:		Line 10:

	[[User:Scalar Tardis\|Scalar Tardis]] 18:58, 28 September 2007 (PDT)		[[User:Scalar Tardis\|Scalar Tardis]] 18:58, 28 September 2007 (PDT)

			== Vertical simulation extent? ==
			* ''Vertical simulation extent has been increased from 768m to 1024m, however script and UI limitations have not yet been changed accordingly yet. ''

			Isn't the vertical simulation extent now 4096 meters?

			When will the UI limitations be updated?

			[[User:Argent Stonecutter\|Argent Stonecutter]] 16:57, 31 March 2008 (PDT)

Scalar Tardis at 02:27, 29 September 2007

2007-09-29T02:27:52Z

← Older revision		Revision as of 19:27, 28 September 2007
Line 2:		Line 2:

	As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it isn't a good idea for the LOD to be able to suddenly degrade from a cylinder to a cube without notifying the scripts. This sudden uinannounced LOD changing will immediately jam the device where the newly formed cube corners overlap where a cylinder or sphere was previously curved.		As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it isn't a good idea for the LOD to be able to suddenly degrade from a cylinder to a cube without notifying the scripts. This sudden uinannounced LOD changing will immediately jam the device where the newly formed cube corners overlap where a cylinder or sphere was previously curved.

	Frequently I am building objects that closely gap the tolerance spacing between objects, and suddenly swapping to a cube shape will only make the collisions completely wrong and potentially even worse until the object explodes.		Frequently I am building objects that closely gap the tolerance spacing between objects, and suddenly swapping to a cube shape will only make the collisions completely wrong and potentially even worse until the object explodes.

Scalar Tardis: update to match sldev mail

2007-09-29T02:27:32Z

update to match sldev mail

← Older revision		Revision as of 19:27, 28 September 2007
Line 1:		Line 1:
	== Need LSL method to monitor LOD changes ==		== Need LSL method to monitor LOD changes ==

	As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it ~~is completely unacceptable~~ for the LOD to degrade from a cylinder to a cube ~~since this~~ will immediately jam the device where the newly formed cube corners ~~are overlapping~~ where ~~the~~ cylinder was curved.		As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it isn't a good idea for the LOD to be able to suddenly degrade from a cylinder to a cube without notifying the scripts. This sudden uinannounced LOD changing will immediately jam the device where the newly formed cube corners overlap where a cylinder or sphere was previously curved.
			Frequently I am building objects that closely gap the tolerance spacing between objects, and suddenly swapping to a cube shape will only make the collisions completely wrong and potentially even worse until the object explodes.

	~~Frequently I am building objects~~ that ~~closely gap~~ the ~~tolerance spacing between objects~~, and ~~suddenly swapping~~ to ~~a cube shape will only make~~ the ~~collisions completely wrong and even worse~~ until the ~~object explodes~~.		We will need the ability to detect these physics LOD changes on the per-prim or per-link-group level so that the scripts driving the impellers, etc, can know there's a problem and can self-deactivate and go non-physical until the LOD goes back up to normal. It's much better to simply sleep the movers until the engine LOD returns to normal.

	~~I need the ability~~ to ~~detect these physics LOD changes on~~ the ~~per-prim level so that the scripts driving the impellers~~, ~~etc, can~~ know ~~there's a problem and can self-deactivate and go non-physical until~~ the ~~LOD goes back up~~ to ~~normal.~~		Also, some sort of visual indication of LOD degrading would be useful to builders. In the beta sandboxes, how am I to know if the incorrect interactions I see are due to actual bugs, or just the sim silently and invisibly substituting cubes in place of all my cylinders and toruses?

	~~This isn't a bug necessarily so it's probably not appropriate to post on~~ the ~~JIRA.~~

	[[User:Scalar Tardis\|Scalar Tardis]] 18:58, 28 September 2007 (PDT)		[[User:Scalar Tardis\|Scalar Tardis]] 18:58, 28 September 2007 (PDT)

Scalar Tardis: New page: == Need LSL method to monitor LOD changes == As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it is completely unacceptable for the LO...

2007-09-29T01:58:13Z

New page: == Need LSL method to monitor LOD changes == As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it is completely unacceptable for the LO...

New page

== Need LSL method to monitor LOD changes ==

As someone who builds lots of complex machines with spinning wheels, rotors, impellers, and so forth, it is completely unacceptable for the LOD to degrade from a cylinder to a cube since this will immediately jam the device where the newly formed cube corners are overlapping where the cylinder was curved.

Frequently I am building objects that closely gap the tolerance spacing between objects, and suddenly swapping to a cube shape will only make the collisions completely wrong and even worse until the object explodes.

I need the ability to detect these physics LOD changes on the per-prim level so that the scripts driving the impellers, etc, can know there's a problem and can self-deactivate and go non-physical until the LOD goes back up to normal.

This isn't a bug necessarily so it's probably not appropriate to post on the JIRA.

[[User:Scalar Tardis|Scalar Tardis]] 18:58, 28 September 2007 (PDT)