ok, so I was playing around with reflections and since my computer dosnt have a high end gfx card, and also, I want to make a game that dosnt need a super computer to run so everyone can play it, I was paying special attention to the effect on the frame rate.
happens that reflections -of course- kill frame rate badly, no surprise here.
what actually surprise me is that this reflections are calculated (or in other words: the frame rate massacre executed) even if the skinmesh is hidden OR, fast your seatbelts: not active!!!
hell, the reflections are calculated and the same number of frame rate affected even if there's no skinmesh with "Visible in reflection" option checked at all, which, in my humble opinion... is quite ridiculous since in this case the only reflection to calculate would be the skybox, which can be perfectly calculated using the cube map file or the value 0.01 in reflection rate, WITHOUT KILLING THE FRAME RATE.
so... after all this... scary revelations, the question is:
is this a bug?
can be fixed?
is pretty horrifying 
happens that reflections -of course- kill frame rate badly, no surprise here.
what actually surprise me is that this reflections are calculated (or in other words: the frame rate massacre executed) even if the skinmesh is hidden OR, fast your seatbelts: not active!!!
hell, the reflections are calculated and the same number of frame rate affected even if there's no skinmesh with "Visible in reflection" option checked at all, which, in my humble opinion... is quite ridiculous since in this case the only reflection to calculate would be the skybox, which can be perfectly calculated using the cube map file or the value 0.01 in reflection rate, WITHOUT KILLING THE FRAME RATE.
so... after all this... scary revelations, the question is:
is this a bug?
can be fixed?
is pretty horrifying 
