Request Rive Feather support in flutter

[madhav2348]

In Flutter, After Adding Feather feature on a simple rectangle give

The following IndexError was thrown during paint(): RangeError (index): Index out of range: index should be less than 2: 2

The following RenderObject was being processed when the exception was fired: RiveRenderObject#cd035: creator: Rive ← RiveAnimation ← SizedBox ← Column ← Center ← KeyedSubtree-[GlobalKey#3b132] ← _BodyBuilder ← MediaQuery ← LayoutId-[<_ScaffoldSlot.body>] ← CustomMultiChildLayout ← _ActionsScope ← Actions ← ⋯ parentData: <none> (can use size) constraints: BoxConstraints(w=500.0, h=500.0) size: Size(500.0, 500.0) This RenderObject has no descendants. ════════════════════════════════════════════════════════════════════════════════════════════════════ 68 Another exception was thrown: RangeError (index): Index out of range: index should be less than 2: 2

sometimes RangeError it goes up to infinity

[YannMarti]

Feather isnt supported yet for flutter. Check this: https://rive.app/docs/feature-support#feathers

[bajabob]

@YannMarti - any idea when it will be supported? We have several assets we have built for a flame game using Rive and need to decide if we are going a different route if feathering is not going to supported soon.

[bajabob]

For documentation purposes, seeing the same error when rendering an asset that uses Rive Feathering. Model will load first base layer of image, then throw the following error:

The following IndexError was thrown during paint():
RangeError (index): Index out of range: index should be less than 2: 2

The relevant error-causing widget was: 
  RenderGameWidget RenderGameWidget:file:///Users/bob/.pub-cache/hosted/pub.dev/flame-1.29.0/lib/src/game/game_widget/game_widget.dart:333:36
When the exception was thrown, this was the stack: 
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 307:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 117:39               _get]
packages/rive/src/rive_core/shapes/paint/fill.dart 14:51                        get fillType
packages/rive/src/rive_core/shapes/paint/fill.dart 40:21                        draw
packages/rive/src/rive_core/shapes/shape.dart 254:11                            draw
packages/rive/src/rive_core/artboard.dart 520:15                                draw
packages/flame_rive/src/rive_component.dart 154:5                               [_paint]
packages/flame_rive/src/rive_component.dart 80:5                                render
packages/flame_rive/src/rive_component.dart 49:5                                render
packages/flame/src/components/core/component.dart 587:5                         renderTree
packages/flame/src/rendering/transform2d_decorator.dart 20:5                    apply
packages/flame/src/rendering/decorator.dart 38:5                                applyChain
packages/flame/src/components/position_component.dart 469:5                     renderTree
packages/flame/src/game/flame_game.dart 144:16                                  renderTree
packages/flame/src/game/flame_game.dart 134:7                                   render
packages/flame/src/game/game_render_box.dart 129:5                              paint
packages/flutter/src/rendering/object.dart 3371:7                               [_paintWithContext]
packages/flutter/src/rendering/object.dart 175:10                               _repaintCompositedChild
packages/flutter/src/rendering/object.dart 120:5                                repaintCompositedChild
packages/flutter/src/rendering/object.dart 1251:31                              flushPaint
packages/flutter/src/rendering/object.dart 1261:14                              flushPaint
packages/flutter/src/rendering/binding.dart 618:5                               drawFrame
packages/flutter/src/widgets/binding.dart 1231:13                               drawFrame
packages/flutter/src/rendering/binding.dart 482:5                               [_handlePersistentFrameCallback]
packages/flutter/src/scheduler/binding.dart 1442:7                              [_invokeFrameCallback]
packages/flutter/src/scheduler/binding.dart 1355:9                              handleDrawFrame
packages/flutter/src/scheduler/binding.dart 1208:5                              [_handleDrawFrame]
lib/_engine/engine/platform_dispatcher.dart 1347:5                              invoke
lib/_engine/engine/platform_dispatcher.dart 301:5                               invokeOnDrawFrame
lib/_engine/engine/initialization.dart 190:36                                   <fn>
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 224:27  _callDartFunctionFast1
The following RenderObject was being processed when the exception was fired: GameRenderBox#e5168
...  needs compositing
...  parentData: <none> (can use size)
...  constraints: BoxConstraints(0.0<=w<=973.0, 0.0<=h<=870.0)
...  layer: OffsetLayer#6e754
...    engine layer: OffsetEngineLayer#b765c
...    handles: 2
...    offset: Offset(0.0, 56.0)
...  size: Size(973.0, 870.0)
RenderObject: GameRenderBox#e5168
  needs compositing
  parentData: <none> (can use size)
  constraints: BoxConstraints(0.0<=w<=973.0, 0.0<=h<=870.0)
  layer: OffsetLayer#6e754
    engine layer: OffsetEngineLayer#b765c
    handles: 2
    offset: Offset(0.0, 56.0)
  size: Size(973.0, 870.0)

Actual visual output:

Expected visual output:

[HayesGordon]

Feathering and all new Rive features are supported in the new rive_native for Flutter package, which is the future version of this Rive Flutter package (it will consume rive_native).

We're encouraging customers to start adopting rive_native. We have a few admin tasks to get this Rive package using rive_native, but the API won't change at this point (docs, migration guides, and tutorials are coming).

Unfortunately, this won't be an easy migration as it is a significant rewrite of how Rive for Flutter works. You can read more here.

[bajabob]

Thanks @HayesGordon! Just cloned the sample project and got it working on my machine.

Do you happen to know if rive_native works with the Flame Engine or is that an integration that still needs to be completed?

[madhav2348]

@HayesGordon Thankyou for your time,
It seems feather feature enhancement may take time

[rsrisai]

@HayesGordon

Thank you for your work and time.

'We're encouraging customers to start adopting rive_native.'

Is this just to have access to earlier API changes? or will it give more control? Or is Rive NON Native going away/not going to be in sync in the future?

[YannMarti]

Feathering and all new Rive features are supported in the new rive_native for Flutter package, which is the future version of this Rive Flutter package (it will consume rive_native).

We're encouraging customers to start adopting rive_native. We have a few admin tasks to get this Rive package using rive_native, but the API won't change at this point (docs, migration guides, and tutorials are coming).

Unfortunately, this won't be an easy migration as it is a significant rewrite of how Rive for Flutter works. You can read more here.

Is rive_native production ready then? Or is it more to try out the new features and shouldnt be used in production yet?

[HayesGordon]

@HayesGordon

Thank you for your work and time.

'We're encouraging customers to start adopting rive_native.'

Is this just to have access to earlier API changes? or will it give more control? Or is Rive NON Native going away/not going to be in sync in the future?

More information is in the links I shared. But rive_native is the future of Rive for Flutter, and it's what this current Rive package will use as well in the near future. The entire current code base (the Dart implementation) for this version of Rive Flutter is no longer actively supported. Support and new features are added to rive_native.

[HayesGordon]

Feathering and all new Rive features are supported in the new rive_native for Flutter package, which is the future version of this Rive Flutter package (it will consume rive_native).
We're encouraging customers to start adopting rive_native. We have a few admin tasks to get this Rive package using rive_native, but the API won't change at this point (docs, migration guides, and tutorials are coming).
Unfortunately, this won't be an easy migration as it is a significant rewrite of how Rive for Flutter works. You can read more here.

Is rive_native production ready then? Or is it more to try out the new features and shouldnt be used in production yet?

The Rive Editor has been using rive_native in production for almost a year now for macOS, Windows, and Web. There may still be platform specific kinks to sort out on iOS and Android, but we encourage adoption so that users can inform us of any issues. But the base code is well tested and used in production.