Example: Adjust wrapped spatial boids interaction radius

This allows the example to run, by avoiding the problematic floating point checks of spatial message wrapped checking

See #1177 for more information

CHANGELOG.md

@@ -59,6 +59,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 + Resolve sign comparison warnings in `test_transform_reduce.cu` under MSVC ([#1247](https://github.com/FLAMEGPU/FLAMEGPU2/pull/1247))
 + Warning fixes ([#1209](https://github.com/FLAMEGPU/FLAMEGPU2/issues/1209))
 + Multiple CI fixes/workarounds ([#1225](https://github.com/FLAMEGPU/FLAMEGPU2/pull/1225), [#1242](https://github.com/FLAMEGPU/FLAMEGPU2/pull/1242))
++ Workaround for wrapped spatial radius bug in `python_native/boids_spatial3D_wrapped` example by changing interaction radius to `0.04` (see [#1177](https://github.com/FLAMEGPU/FLAMEGPU2/issues/1177)).
 
 ## [2.0.0-rc.1] - 2024-01-12
 

examples/python_native/boids_spatial3D_wrapped/boids_spatial3D.py

@@ -292,7 +292,7 @@ def inputdata(message_in: pyflamegpu.MessageSpatial3D, message_out: pyflamegpu.M
 env.newPropertyFloat("MIN_INITIAL_SPEED", 0.1)
 
 # Interaction radius
-env.newPropertyFloat("INTERACTION_RADIUS", 0.05)
+env.newPropertyFloat("INTERACTION_RADIUS", 0.04)  # 0.04 is a workaround for wrapped spatial messaging bug
 env.newPropertyFloat("SEPARATION_RADIUS", 0.01)
 
 # Global Scalers