But, we did. It's present under important information in the opening post:
I'm sorry, I was stupid and also forgot to write version 5.1 works fine, but 5.2,5.3,5.4 does not work. Is this just a problem for me or someone else?But, we did. It's present under important information in the opening post:
View attachment 2932649
Still, we'll take the feedback and try to improve its visibility some more. Thank you
The change to a Chromium 110+ version of NW.js (0.73+) means that it won't work in Windows 8 or 8.1 either, for what it's worth.But, we did. It's present under important information in the opening post:
...
Still, we'll take the feedback and try to improve its visibility some more. Thank you
We realize that you mentioned the error language, but could you also screenshot it? Also, would you mind sharing your PC specs? You can DM it to us directly if you like.
Thank you for pointing that out. We had doubts about issues with 8.1 as well but couldn't find any user with that particular OS who could test and confirm that theory. Huinyaaa's issue does seem to be stemming from the same source, but it's always better to clarify.
Hello again. After doing some research and running queries around, we've come to the regrettable conclusion that you also seem to be affected by the same incompatibility development as Windows 7 users are. Nw.dll error at the end there is a bit of a giveaway as it is linked to the node build updates. Furthermore, after taking your specs into equation as well as the VirtualMemoryDiscarding error log, it leaves almost no doubt that this is a Kernel32 related issue.
bad very bad fucking Microsoft has no complaints against you. I can only ask Try to make a game on Unity, try maybe Unity will work out, it seems like it doesn’t require large versions of Windows yet and Unity treats animations more softly than the MV makerHello again. After doing some research and running queries around, we've come to the regrettable conclusion that you also seem to be affected by the same incompatibility development as Windows 7 users are. Nw.dll error at the end there is a bit of a giveaway as it is linked to the node build updates. Furthermore, after taking your specs into equation as well as the VirtualMemoryDiscarding error log, it leaves almost no doubt that this is a Kernel32 related issue.
We are fairly confident that slowly, but surely legacy OSes like 7/8.1 are losing software support. Unfortunately, not much of a solution we can offer you at this time. With the slow march of time, near 10 year old systems like yours are being left behind and with the high system requirements for latest OSes like Win 11, it just isn't a viable solution to recommend an upgrade.
Sincerest apologies
The current version of Unity (2023.1) also requires Windows 10 (64-bit) or 11. Which, if you'd like, you can still upgrade to from Windows 7/8/8.1.
explanatory team please I'm doing something wrong or do you have better ideas? If I offended you in any way, I apologize
Unity just announced they'll charge devs $0.20 per install after the game they made in Unity passes a threshold (200k revenue and installs for the free version, 1M for the Pro version) from January 1st 2024 onwards
Basic requirement check first: Are you positive you have your bounty licence? If so, are you sure you're finished with the Xaide content completely? Both of these are necessary precursors to the new quest.
We modified a lot in terms of how the game loads files and it uses specific call functions that are only available on windows, that sadly aren't modified/adjusted for other platforms yet. Sorry for the inconvenience.
I've done Xaide already, last thing i did for bounty is to collect the flower and bring it back to the barman. Now he's telling me there's no other bounty.
If the guild-master is telling you that there are no new quests, fair chance one of the requirements is still pending.
