Build 295.10 - Release Version

It is good to hear you are recovering Yves , take it easy!

Quick reminder:

Please login to see this attachment.

You should change this... unless the community owns Fusion 2.5 now lol

That's...not how copyright works.

Fusion should have a built-in function lerp(x,y,amount)

CTF must have a custom qualifier creating system.

Quote from OyunKaosu

CTF must have a custom qualifier creating system.

You can create your own qualifiers with Fusion + DLC

Quote from Xenon3000

You can create your own qualifiers with Fusion + DLC

Would be great if they were more like a "class" with their own independent variables, through. That way it would be possible to apply these classes/qualifiers to any object without any variable conflicts

Quote from willy

Would be great if they were more like a "class" with their own independent variables, through. That way it would be possible to apply these classes/qualifiers to any object without any variable conflicts

Yes ! with alterable values and behaviors !

Since Build 296 is taking a while, I'd like to report a graphical issue found with Build 295. It would be nice to have this fixed in 296. Here's how to reproduce it:

1. Create a new application.
2. In Window properties, set window size to 1280x720, resize the frame too. Set a background color.
3. Disable "Heading", "Menu bar" and "Menu displayed on boot-up".
4. In Windows properties, enable "DPI aware".

When you run the application from the editor, there will be a gap on the bottom right, and the graphics will be squished. I've only seen this happen with the 1280x720 resolution. 1280x721 or 1280x719 works fine.

There is an option for objects called "Inactivate if too far from window". It’s a useful feature, but it should have more configuration options.

According to the Help description:

• Automatic: Objects specified in collision detection conditions are not inactivated. All other objects are inactivated.
• Yes: Always inactivates if far from the window.
• No: Never inactivates.

What does it deactivate?

"The object is not destroyed, but stops moving and reacting with collisions."

Technically, the object isn’t destroyed, but it triggers the built-in fade-in animation, which is strange.

This function should have more configuration options:

• Ability to set the deactivation distance.
• Option to choose whether to deactivate movement, collisions, or even an option to destroy the object when exceeding the distance (this would be very useful for things like particles).
• An option to disable all events of the object when outside a selected area.
• An event in the event editor that allows full control over modifying these settings dynamically.

Is it possible to enter only numbers in an edit box. Thanks

Sure, here it is. I use an AMD GPU if that helps.

I made an example of how zoom could work in fusion, unfortunately it only works on dx11 because the scaling is different in dx9. Unfortunately, resizing the window is only possible when it is minimized

Please login to see this attachment.

Is there a chance of a built-in zoom function in the future?

Quote from PkR

Sure, here it is. I use an AMD GPU if that helps.

Quote from Yves

Works fine...

I have AMD GPU and it works fine too

Quote from TonyThunder

I have AMD GPU and it works fine too

I have NVIDIA GPU and it works fine for me, also.

Quote from Fadzior

I made an example of how zoom could work in fusion, unfortunately it only works on dx11 because the scaling is different in dx9. Unfortunately, resizing the window is only possible when it is minimized

Please login to see this attachment.

Is there a chance of a built-in zoom function in the future?

This flashes between every resizing on my end and is disorienting--am using NVIDIA GPU for DX11. Does it do that on your end?

EDIT: This only happens on my ultrawide monitor. If I move to regular widescreen 1920x1080 monitor it operates smoothly to match the event actions you have setup. Perhaps if there is a way to get the resolution of the monitor and set the floating point numbers accordingly somehow this would be a viable solution.

Quote from Yves

No problem here with the instructions you mentioned. Could you post a MFA please?

Hi Yves
What exactly is going on with 296? What's in it that is taking so long? Any big changes we can look forward to?

The reason's posted upthread a page or two back, it's not been much longer since.