I think the point is raise it to the minimum version which supports the
codebase. If there was some feature in 2.10 that did not exist in 2.6 and
that feature was required for proper execution, then 2.10 would be a better
target. Otherwise it would just be forcing people to upgrade who would not
ot
Is this a bug ?
Or missinf functinality ?
But if im try to use ground sit on sculpt am always ending on the
terrain below.
If i do ground sit on flat normal prim it works fine.
Like to know if its wrong before am makeing a useless mantis.
___
Opensim
I also second 2.10 as a base, but I think 3.0 is a bit to soon since that
version is not yet available in a lot of stable linux repo's.
On 26 jan. 2013, at 20:51, Ilan Tochner wrote:
> I second setting 2.10 as the base. If we'll be forcing people to upgrade I
> think we should upgrade to the
This implementation will work for physics. The physics engine cannot reference
Scene (circular reference madness) so, on creation of the scene's physics
instance, I will pass in the instance of DAMap (since it is defined in
OpenSim.Framework) much the same way the asset request method instance i
I second setting 2.10 as the base. If we'll be forcing people to upgrade I
think we should upgrade to the latest stable release and not to one that is
outdated.
If OpenSim works fine with 3.0 then I'd vote for it to be the base. If
we're still calling OpenSim alpha we should at least get the benef
if we can get a way with it why not go to 2.10 else quickly be out of date
agian
On Sat, Jan 26, 2013 at 9:38 AM, James Hughes wrote:
> +1
>
> On 01/24/2013 10:29 PM, Justin Clark-Casey wrote:
>
>> Whilst writing JsonStore regression tests this evening, I hit the
>> problem where modInvoke scrip
+1
On 01/24/2013 10:29 PM, Justin Clark-Casey wrote:
Whilst writing JsonStore regression tests this evening, I hit the
problem where modInvoke script methods of more than 4 parameters cannot
be registered on Mono 2.4.3 as it doesn't implement the required larger
multi-parameter Func generic types