User:LaniGlobal - Revision history

LaniGlobal: /* LANI GLOBAL SYSTEMS Twitter feed */

2017-10-28T01:51:46Z

‎LANI GLOBAL SYSTEMS Twitter feed

LaniGlobal: /* Determining Physics Engine by Script Functions */

2017-07-16T18:32:10Z

‎Determining Physics Engine by Script Functions

LaniGlobal: /* Lani Global Stops Making Products for OpenSim */ update September 2015

2015-09-16T14:29:13Z

‎Lani Global Stops Making Products for OpenSim: update September 2015

LaniGlobal: /* Determining Physics Engine by Script Functions */ link to mantis about llGetEnv

2015-04-14T16:09:43Z

‎Determining Physics Engine by Script Functions: link to mantis about llGetEnv

LaniGlobal: /* Determining Physics Engine by Script Functions */

2015-04-14T15:54:17Z

‎Determining Physics Engine by Script Functions

LaniGlobal: /* Determining Physics Engine by Script Functions */ added llGetEnv test unit

2015-04-13T22:15:10Z

‎Determining Physics Engine by Script Functions: added llGetEnv test unit

LaniGlobal: /* Determining Physics Engine by Script Functions */

2015-04-13T06:26:55Z

‎Determining Physics Engine by Script Functions

LaniGlobal: /* Deprecation of ODE and Evolution of Physical Vehicles */

2015-04-13T06:22:34Z

‎Deprecation of ODE and Evolution of Physical Vehicles

LaniGlobal: /* Why Is My Stuff Broken? */

2015-04-11T20:01:02Z

‎Why Is My Stuff Broken?

LaniGlobal: /* Why Is My Stuff Broken? */ added text

2015-04-11T20:00:06Z

‎Why Is My Stuff Broken?: added text

@@ Line 5: / Line 5: @@
 '''Lani Global Systems on Twitter http://twitter.com/LaniGlobal
-Tweets mainly covering OpenSim, OSGrid, HyperGrid, and 3D Virtual Worlds.
+Lani tweets about anything that amuses her.
 == '''Lani Global OSGrid Photo Gallery ==

← Older revision		Revision as of 18:32, 16 July 2017
Line 1,316:		Line 1,316:

	= '''Determining Physics Engine by Script Functions''' =		= '''Determining Physics Engine by Script Functions''' =
		+
		+	'''NOTE July 2017'''
		+
		+	A solution to this problem has been implemented in OpenSim.
		+	see
		+	string osGetPhysicsEngineName()
		+	[[http://opensimulator.org/wiki/OsGetPhysicsEngineName]]
		+
		+	The OpenSim Mantis report can be viewed here:
		+	[[http://opensimulator.org/mantis/view.php?id=7528]]

	'''Since multiple Physics Engines are available on a modular basis in OpenSim, there is a need for scripted objects to self-discover which Physics Engine is active in a region.''' The OSSL function OsGetPhysicsEngineType is available in regions which have OSSL allowed and authorized for access of the function by the user. However, OSSL is not universally authorized to all users who have script allowed. This is needed for viable content creation and product manufacture of physical scripted objects, such as vehicles which run solely LSL script. Therefore, I propose that an LSL function be modified and extended with some additional flag or value so that it can be utilized.		'''Since multiple Physics Engines are available on a modular basis in OpenSim, there is a need for scripted objects to self-discover which Physics Engine is active in a region.''' The OSSL function OsGetPhysicsEngineType is available in regions which have OSSL allowed and authorized for access of the function by the user. However, OSSL is not universally authorized to all users who have script allowed. This is needed for viable content creation and product manufacture of physical scripted objects, such as vehicles which run solely LSL script. Therefore, I propose that an LSL function be modified and extended with some additional flag or value so that it can be utilized.

@@ Line 1,258: / Line 1,258: @@
 '''I won't be doing any crowdfund promotion or instigation.''' Most core OpenSim developers see it as an experimental project, not as a content platform... and therein lies a juxtaposition of user interest. So, no matter whether something is fixed in the near term... something else is only a patch away from being broken in next month's release. The OpenSim devs who are concerned about such things as continuity are only those who run their own for-profit grids, and they carefully manage their own proprietary versions of OpenSim simulator code that runs on their grid. I'm not disparaging OpenSim developers, far from it, I have the deepest respect and awe for what has been accomplished. It's just that there are many developers and each has a different level of expertise, direction of importance, and area of interest. After all, if I want something fixed in OpenSim, I can write my own patch for it. What a wonderful system!
-−
 = '''The End of ODE in OpenSim and The Rise of Bullet Sim Physics''' =

@@ Line 1,316: / Line 1,316: @@
 One possibility for an OpenSimulator extension of an LSL script function to determine Physics Engine, is the llGetEnv function.
 == '''llGetEnv Test Unit''' ==
@@ Line 1,322: / Line 1,324: @@
 Returns a string with the requested data about the region.
 • string name – The name of the data to request
-Note that the value returned is a string, you may need to cast it to an integer for use in calculations.
+• string name – The name of the data to request.
 [http://wiki.secondlife.com/wiki/LlGetEnv More information on the llGetEnv function]

@@ Line 1,313: / Line 1,313: @@
 = '''Determining Physics Engine by Script Functions''' =
-'''Since multiple Physics Engines are available on a modular basis in OpenSim, there is a need for scripted objects to self-determine which Physics Engine is active in a region.''' The OSSL function OsGetPhysicsEngineType is available in regions which have OSSL allowed and authorized for access of the function by the user. However, OSSL is not universally authorized to all users who have script allowed. This is needed for viable content creation and product manufacture of physical scripted objects, such as vehicles which run solely LSL script. Therefore, I propose that an LSL function be modified and extended with some additional flag or value so that it can be utilized.
+'''Since multiple Physics Engines are available on a modular basis in OpenSim, there is a need for scripted objects to self-discover which Physics Engine is active in a region.''' The OSSL function OsGetPhysicsEngineType is available in regions which have OSSL allowed and authorized for access of the function by the user. However, OSSL is not universally authorized to all users who have script allowed. This is needed for viable content creation and product manufacture of physical scripted objects, such as vehicles which run solely LSL script. Therefore, I propose that an LSL function be modified and extended with some additional flag or value so that it can be utilized.
 One possibility for an OpenSimulator extension of an LSL script function to determine Physics Engine, is the llGetEnv function.

@@ Line 1,313: / Line 1,313: @@
 = '''Determining Physics Engine by Script Functions''' =
-'''Since multiple Physics Engines are available in OpenSim, there is a need for scripted objects to self-determine which Physics Engine is active in a region.''' The OSSL function OsGetPhysicsEngineType is available in regions which have OSSL allowed and authorized for access of the function by the user. However, OSSL is not universally authorized to all users who have script allowed. Therefore, I propose that some LSL function be modified with some addition flag or value so that it can be utilized. One possibility is the llGetEnv function.
+'''Since multiple Physics Engines are available on a modular basis in OpenSim, there is a need for scripted objects to self-determine which Physics Engine is active in a region.''' The OSSL function OsGetPhysicsEngineType is available in regions which have OSSL allowed and authorized for access of the function by the user. However, OSSL is not universally authorized to all users who have script allowed. This is needed for viable content creation and product manufacture of physical scripted objects, such as vehicles which run solely LSL script. Therefore, I propose that an LSL function be modified and extended with some additional flag or value so that it can be utilized.
-Another posisible method is, for example, one of the ancient deprecated flags in the LSL function llGetRegionFlags() could be newly implemented in OpenSim simulator code. To explore this further, I made a Region Flags Test Unit.
+One possibility for an OpenSimulator extension of an LSL script function to determine Physics Engine, is the llGetEnv function.
 == '''llGetEnv Test Unit''' ==
 == '''Region Flags Test Unit''' ==
 '''A script for testing region flags, using the function llGetRegionFlags()''' is offered below. Drop the script into a prim and touch it. It will say the total value of region flag and the hex value of every possible region flag hex bit.
 <source lang="lsl">
-//llGetRegionFlags Test Unit
+// llGetRegionFlags Test Unit
 // (C)2015 LANI GLOBAL SYSTEMS. Offered Under License:CC-BY-SA
 // APRIL 2015

← Older revision		Revision as of 06:26, 13 April 2015
Line 1,316:		Line 1,316:

	Another posisible method is, for example, one of the ancient deprecated flags in the LSL function llGetRegionFlags() could be newly implemented in OpenSim simulator code. To explore this further, I made a Region Flags Test Unit.		Another posisible method is, for example, one of the ancient deprecated flags in the LSL function llGetRegionFlags() could be newly implemented in OpenSim simulator code. To explore this further, I made a Region Flags Test Unit.
		+
		+	== '''llGetEnv Test Unit''' ==
		+

	== '''Region Flags Test Unit''' ==		== '''Region Flags Test Unit''' ==

@@ Line 1,271: / Line 1,271: @@
 == '''Deprecation of ODE and Evolution of Physical Vehicles''' ==
-'''Oddly enough, a recent crowdfund to fix a core OpenSim feature related to physics caused some ODE products to fail :)''' One of the areas that I've worked to advance in OpenSim, is Physical Vehicles for ODE. The vehicle category was cited in numerous HyperGrid Business polls. As you may know, statistics are one of my interests. HyperGrid Business polls of users over the last few years showed that Physical Vehicles were at the top of the desired list of features and functions for OpenSim. So, I worked within the coder & content creator community to develop a kit for vehicles. Prior to that work, the default for maximum physical prim size in OpenSim was 10 metres. This affectively made it impossible to make larger to-scale vehicle products. That default was changed to 64 metres size, which enabled multi-passenger physical vehicles to be marketed to mainstream. Oddly enough, there was a lot of resistance to that change by the OpenSim developer community. I lobbied and cajoled many core OpenSim developers for over a year, even published scientific tests and graphs, and then submitted the changes as a "patch" to the OpenSim code myself. It was finally accepted and became the default in OpenSim, ironically because it was compatible with new Bullet capabilities, which had progressed by then. Thus, we now have multi-passenger airplanes, ships, boats, helicopters, spacecraft, cars, etc. Reference: my campaign for multi-passenger physical vehicles in OpenSim
+'''Oddly enough, a recent crowdfund to fix a core OpenSim feature related to physics caused some ODE products to fail :)''' One of the areas that I've worked to advance in OpenSim, is Physical Vehicles for ODE. The vehicle category was cited as "most popular" in numerous HyperGrid Business polls. HyperGrid Business polls of users over the last few years showed that Physical Vehicles were at the top of the desired list of features and functions for OpenSim. So, I worked within the coder & content creator community to develop a kit for vehicles. Prior to that work, the default for maximum physical prim size in OpenSim was 10 metres. This affectively made it impossible to make larger to-scale vehicle products. That default was changed to 64 metres size, which enabled multi-passenger physical vehicles to be marketed to mainstream. Oddly enough, there was a lot of resistance to that change by the OpenSim developer community. I lobbied and cajoled many core OpenSim developers for over a year, even published scientific tests and graphs, and then submitted the changes as a "patch" to the OpenSim code myself. It was finally accepted and became the default in OpenSim, ironically because it was compatible with new Bullet capabilities, which had progressed by then. Thus, we now have multi-passenger airplanes, ships, boats, helicopters, spacecraft, cars, etc. Reference: my campaign for multi-passenger physical vehicles in OpenSim
 http://opensimulator.org/wiki/User:LaniGlobal#OpenSim_Change-Advocacy_Projects
 '''Now we are moving into a brand new phase of content made for OpenSim that is designed only for Bullet Physics, since ODE has been "defacto deprecated", which is developer-speak for "abandoned".''' So, core OpenSim content that was made prior to 2015 that uses physics must be either thrown away or modified to be compatible. In some cases, the ODE-based content may be broken, even if the simulator owner has selected the ODE engine for their region. Some OpenSim grids still run entirely on ODE, and have made proprietary improvements to it that rival the performance of Bullet. Indeed, there may be some advantages to ODE, such as reduced server memory requirements. Even though, many believe Bullet performance is superior, and it probably is in many ways. In my case, I don't take sides on which is superior. My philosophy has always been, to design creative content for the mainstream user.
 == '''Dealing With Physical Vehicle Compatibility Issues for Reference Designs''' ==

@@ Line 1,253: / Line 1,253: @@
 == '''Why Is My Stuff Broken?''' ==
-'''For thousands of users, when their stuff doesn't work, they don't know why.. and they just think it is crap.''' The cause may be changes in the simulator server, or changes in the scripts, or the way prims or mesh perform. Backwards compatibility is often not paid attention to. When there is a proprietary interest, or moneyed interest in a business, such things would be carefully weighed. But, with a volunteers who write the code for free, the resources may not be available to keep track of everything.
+'''For thousands of users, when their stuff doesn't work, they don't know why.. and they just think it is crap.''' The cause may be changes in the simulator server, or changes in the scripts, or the way prims or mesh perform. Backwards compatibility is often not paid attention to. When there is a proprietary interest, or moneyed interest in a business, such things would be carefully weighed. But, when volunteers write the code for free, the resources may not be available to keep track of everything, or test it.
 == '''What Can Be Done About It?''' ==