halu
halu
Explore posts from servers
MMechaKeys
Created by iandroidgamingalt on 6/30/2024 in #mechakeys-help
no internet
thats really weird… i believe people have complained about similar issues in the subway or when closing and returning to their laptops, which makes sense as both instances involve connection interruptions your situation seems a bit more or peculiar and haven’t heard of any similar complaints so far… so unfortunately im not so sure how to help if your able to sync, claim, and download soundpacks, you should prob be able just ignore the errors as you have most of the functionality
10 replies
MMechaKeys
Created by .lifly on 7/2/2024 in #mechakeys-help
major performance issues
mechvibes is essentially the same tech under the hood. it would be weird for them to behave differently. 1khz might be a tad much depending on ur computer. I’ll try some different tech to see if anything else performs better and i’ll see if theres a way to detect this flooding/back-pressure situation in future versions. i dont have any immediate fixes tho aside from what was already mentioned
12 replies
MMechaKeys
Created by Leon on 7/1/2024 in #mechakeys-help
i was about to get omipoint b but it laged and i bouth gateron brown can i please get an refound
meh, sure why not
8 replies
MMechaKeys
Created by .lifly on 7/2/2024 in #mechakeys-help
major performance issues
You might want to increase the apps priority in task manager. the other causes for this involves flooding inputs: - mouse polling rate is too high - ur using and auto-clicker or some other input assistant
12 replies
MMechaKeys
Created by iandroidgamingalt on 6/30/2024 in #mechakeys-help
no internet
hmm not sure. does this happen when the app is open or after returning to your computer? do any api’s work? can you claim achievements and sync or do you always get this message? ( if there’s abnormal behavior, its usually due to antivirus/firewall blocking requests or a misconfigured DNS server, or you live in Turkey… )
10 replies
MMechaKeys
Created by extendify on 6/30/2024 in #mechakeys-help
email not received
its a known glitch in the old version. theres no intention to fix anything on that version
19 replies
MMechaKeys
Created by extendify on 6/30/2024 in #mechakeys-help
email not received
that’s incredibly sus
19 replies
MMechaKeys
Created by extendify on 6/30/2024 in #mechakeys-help
email not received
if thats you, all is good ig
19 replies
MMechaKeys
Created by extendify on 6/30/2024 in #mechakeys-help
email not received
that, shouldn’t be possible? hmmm
19 replies
MMechaKeys
Created by extendify on 6/30/2024 in #mechakeys-help
email not received
use #v2-download to verify email is spelt correctly or try to make a new account with the same email
19 replies
MMechaKeys
Created by 𝙙𝙖𝙠𝙤𝙞 on 6/30/2024 in #mechakeys-help
Camera problems in games when activating mouse sounds
2 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
oh is that what the v135 prevents?
11 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
tho... if the primitives solid dep gets bumped, then i'll end up with two versions again
11 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
i just started pinning my versions, hopefully that helps
11 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
much appreciated, thank you!
11 replies
SSolidJS
Created by halu on 6/20/2024 in #support
SOLVED: Non-Reactive Memo for Reactive Values?
13 replies
SSolidJS
Created by halu on 6/20/2024 in #support
SOLVED: Non-Reactive Memo for Reactive Values?
tldr - effect runs twice to dispose itself and is recreated as necessary when recalculate on demand
13 replies
SSolidJS
Created by halu on 6/20/2024 in #support
SOLVED: Non-Reactive Memo for Reactive Values?
turns out lazyMemo primitive wasn't working in my production use-case... This is what i had to do to eliminate the watcher/on() pattern: https://playground.solidjs.com/anonymous/8dc85006-f489-46b1-887a-18d1f9c7812f
function memo<T>(cb: () => any) {
/*
The goal of this memo is to minimize recalculations,
yet still supply a syncronized value on demand.
- The only way to minimize recalculation on demand in this scenario
is to track whether dependancies go dirty (recalc required).
- Avoiding recalc on reactive updates means the
subscriptions will be cleared and the effect disposed.
This actually eliminates unnecesary side-effects entirely,
but requires the effect be re-initialized each recalculation.
*/
let [last_val, set_last] = createSignal<T>();
let is_dirty = true;

let owner = getOwner();
let effect = () => {
runWithOwner(owner, () => {
createComputed(() => {
if (is_dirty) {
console.log("recalc");
// run, memo, and mark clean
set_last(cb());
is_dirty = false;
} else {
console.log("made dirty");
// Dispose effect:
// no need to listen to subsequent updates once known to be dirty
is_dirty = true;
}
});
});
};
effect();

return () => {
// if dirty, recalc on demand
// init new comp. to listen for dirty toggle
if (is_dirty) effect();
return last_val(); // return clean memo
};
}
function memo<T>(cb: () => any) {
/*
The goal of this memo is to minimize recalculations,
yet still supply a syncronized value on demand.
- The only way to minimize recalculation on demand in this scenario
is to track whether dependancies go dirty (recalc required).
- Avoiding recalc on reactive updates means the
subscriptions will be cleared and the effect disposed.
This actually eliminates unnecesary side-effects entirely,
but requires the effect be re-initialized each recalculation.
*/
let [last_val, set_last] = createSignal<T>();
let is_dirty = true;

let owner = getOwner();
let effect = () => {
runWithOwner(owner, () => {
createComputed(() => {
if (is_dirty) {
console.log("recalc");
// run, memo, and mark clean
set_last(cb());
is_dirty = false;
} else {
console.log("made dirty");
// Dispose effect:
// no need to listen to subsequent updates once known to be dirty
is_dirty = true;
}
});
});
};
effect();

return () => {
// if dirty, recalc on demand
// init new comp. to listen for dirty toggle
if (is_dirty) effect();
return last_val(); // return clean memo
};
}
(did this mostly for fun, not sure I'd actually use it)
13 replies