Casper Fabricius
Casper Fabricius
I've tried to get this component to work with A-Frame 0.2.0, but it doesn't work. This example just renders a white cube with A-Frame 0.2.0 and version 1.4.0 of this...
Thanks for checking, @ngokevin In my example it is simple to avoid detaching/attaching entities and instead just toggle the visibility. However, my actual Aframe/React app is a lot more complex,...
I just noticed that the `raycaster` has a `refreshObjects` method. Should this be called whenever React re-renders?
It does not fix it for me, unfortunately.
@ip I'm not sure. I am currently tracking down performance issues that might be related to having to remove the limitation on the raycasting, but it's too early to say...
Update: This appears not to be an issue with `aframe-react`, but with `aframe` itself. With 0.5.0, scoped raycasting using `objects` works and there I experience no performance problem. With newest...
With the latest A-Frame master, filtering the raycaster using `objects: .interactable` works as expected for me, both for laser controls and cursor.
Same issue here: ``` carpet = Redcarpet::Markdown.new(Redcarpet::Render::HTML.new) carpet.render('*test **test** test*') => "test *test** test*\n" ```