Ok, I will
Ok, I will
Did something changed on the saving routine of Android runtime? (API 30, target Android 10)
Suddenly my project can't save files on the root of External Storage ( ExternalStorageDirectory$( "Android object" ) + "/teste.png" )
Saving with List object redirects it to Download folder and creating a file with File object with a path and filename already defined opens the save dialog...
Something seems off...
This part of the new Play Sample (all parameters) action doesn't really make sense to me. Why is the default value lower than the minimum value?
Ive run into an issue, if i set all channels volume to 0 (or whatever) but then use the action "play sample" so fusion picks a free channel; fusion plays it at full volume. If i specify a channel it plays it at the right volume.
Is this by design? Its creating some issues for my right now since sounds will cut each other off if i specify channels and they play at a rapid succession.
I hadn't thought that it would relate to the file's sampling frequency (44.1khz as you suggested). I assumed that this was strictly about pitch, whereas the sampling frequency is about fidelity. But now that I think about it, of course Fusion can't know what the pitch of your sound should be since it'll vary from moment to moment. So I'm sure you're right. And I guess that if we know the sampling frequency of our file, then we can easily work out the pitch from there (if it's 44.1k then 88.2k will be an octave higher, 22.05k an octave lower, etc.)
Is testing your game using "Build and Run" on PC supposed to be essentially identical to running it by double-clicking the EXE? I always assumed so. Though I've noticed that when I Build and Run a EXE, then quit Fusion, Steam won't let me reopen Fusion because it says Fusion is already running. I have to quit my EXE first, and only then Steam will let me open Fusion. I don't know if this is an issue or not, but I thought I'd bring it up.
Always thought the same thing about build and run. Its odd that steam version is not letting you reopen Fusion like that. The standalone version lets you run multiple instances of Fusion at the same time.
Speaking of the Steam version being prickly, I've noticed recently that I can't use Fusion by double-clicking ...\Clickteam Fusion 2.5\mmf2u.exe. If I do, then it usually gives me this error when I try and run my MFAs:
Instead of running mmf2u.exe I have to launch Fusion by running steam://rungameid/248170, or from the start menu (which I normally do anyway - and which also uses steam://rungameid/248170). I feel like this is new. Maybe it isn't, but I'm almost certain I would have noticed at some stage over the past 7 years if running mmf2u.exe didn't work.
ok, maybe this is me not understanding how things are supposed to work again, but I have another comment about the new Play Sample (all parameters) action. I assumed that the value you set for the "volume" will be the sample volume, but it's the channel volume (it permanently changes the volume for all subsequent sounds played on that channel). If this is how it's supposed to be, then can the titlebar text at least be modified to Channel Volume: minimum=0, maximum=100 for clarity?
If this is how it's supposed to be, then fine, but what happens if you choose the channel 0 (first available)? Will the "volume" setting still change the channel volume? If so, then that seems like a bug/flaw to me: it'll be permanently changing the volume of effectively random channels without you easily knowing which they are. Do this a few times, and now you've got an unpredictable mess of different volumes throughout your channels. Let's say you use track 1 for dialogue. At some point, everyone stops talking, the channel becomes free, and some other sound is assigned this channel for a moment, and permanently changes its volume to 30. Now, whenever your dialogue starts again, it'll be too soft, at volume 30.
It seems to me that the moment you start to play any sample on channel "0" with an explicitly stated volume, you're effectively forcing yourself to always explicitly stipulate the volume of every sample you play on any channel from that point onwards, otherwise you run the risk of something playing at the wrong volume. Is this expected behaviour?