Ooops.8694

Small update after days of experimenting with Wine and Proton and after getting the game running again: There are many here seemingly doing the same thing or running the same version with varying success, so maybe someone with more clue about the details can make sense out of this. For me it's not actually about the Wine or DXVK version used but the prefix... - Existing Wine prefix crashes. - Freshly created Wine prefix with DXVK set up crashes. - Prefix created with Proton works with Wine afterwards (after setting up DXVK for it). Tested with wine-staging7.13/wine-ge-custom7.22 and DXVK1.10.1/1.10.2 in all combinations. Reproducible on 3 different devices (nvidia, amd and intel graphics)....

Tested on my regular pc (amd) and on laptop (nvidia515.57/intel). Same crash, so not exactly card related...

That's a nice in theory but no. wine-ge 7.21 (two days old release) with DXVK 1.10.2 (a week old) crashes instantly on launcher start.

The fact that the icon randomly persists through some cutscenes when the whole UI is hidden still makes me believe that it is not exactly behaving as intended...

And I'm telling you it's pointless unless you get yourself a couple of friends who provide all the boons for your test. Arc is not updated and the ingame message does not distinguish dps sources, so saying i'm doing for example 30k on the golem is useless. If you neither have precise number for the mech part of that dps nor know how it would behave fully buffed that's just random guessing.

You can't even test it properly without employing an army of friends... They changed the mech to inherit you stats but not your stat increases from boons (so there's no getting power for might on the engineer then getting more for might on the mech) and at the same time added a "copy every boon you get to mech"-function to shift signet. But that effect does not trigger on boons in the test area. So either you get a bunch of people to provide the boons to do a realistic test or you're testing with a boonless mech that should have capped might/fury/quickness/alacrity.

Is your system using ibus by default? That one likes to fail relaying properly timed keypresses to wine for me all the time...

While that's a nice idea as an alternative, AHK runs perfectly well in Wine. The normal winetricks package can even autoinstall it on your prefix...

Just a small note (maybe more relevant in the future, when more people upgrade to newer wine versions):There's a bug at the moment, preventing players using wine 6.3 and above (standard and staging) to login to the game. Connections generally work (you can download/update the client via launcher for example), but the login server in unreachable.

Be careful with telling people this toxicity primarily exists in the forum or that those complaining are the same ones insisting on their strange open world build and unwilling to adapt. Such posts in this thread will get deleted...

But how are you even posting here? I couldn't log into the forum while the ingame login was down and it's been like this as long as i remember... So up to now i assumed all logins run thorugh the same server. looking confused

Fine you can clear raids once a week for some rewards... and after those 3-4 hours/week (probably much less if you're not pugging^^) you can't even use food/stuff or you are paying instead of earning something.

...and yet the wiki says exactly that: summons count as companions for this rune, as do minions and temporary things from runes (golemancer for example) or potions.And i'm pretty sure, they worked at some time in the game. So i would say yes, they do.Guess it's time for some testing...

Maybe i misunderstand your post but wine-5.19 and wine-staging-5.19 are not the same at all. While staging is used as a testing area for wine it's not some development-version in a classical sense where wine-staging-x.y is "promoted" to wine-x.y when it's deemed stable enough.Wine-staging is a separate special set of patches to be applied on top of wine, often to fix special problems/performance issues, sometimes with only a single game. Some of these patches are experimental or even quite "hacky" and while some of the staging stuff later finds it's way into the regular version there are some quick fixes that were never really meant to be kept but just temporarily "plug some hole" until a proper stable patch exists.So of course wine and wine-staging have the same version number. That's how it's supposed to be: Every wine-staging version has the same number as the regular version it's based on, then adds some patches (which can be added separately too instead of applying them all as many package maintainers do for the repos).And because of this wine and wine-staging with identical version numbers may have very different levels of stability/performance for many games and you should probably always use the staging branch if you're after the best possible performance... PS: Speaking of experimental patches... Can someone confirm arcdps being broken on wine-staging-5.19? I had no time yet to do extensive tests to see if the problem lies in wine-staging alone (5.18 and earlier still works) or if it's also related to nvidia being nvidia and not providing a working driver for the up-to-date kernel...

I can only speak from the arch perspective, but didn't even know a dedicated wine32 existed. I use the same wine package for 32 and 64bit winearchs (or i should say i used the same wine. nowadays i compile one of the tkg builds myself, since wine-staging dropped esync support while they do some extensive rewrites.) All you need are the 32bit libraries.Those are contained in the multilib repository and i'm pretty sure they exist for manjaro the same way they do for arch. They may not be included with the things pacman checks for by default, but that's only a matter of opening /etc/pacman.conf, scrolling down and deleting "#" before [multilib] so they get checked too. More problematic will probably be the fact that you really want wine-staging for esync support. I never tried on my normal pc but on this rather old laptop i'm working from at the moment esync makes the difference between unplayable 6-10 frames at best and solid 30-50 while moving in populated areas. And as i mentioned before that's not supported at the moment on newer versions of wine-staging (i think the last one with esync support was 5.9 and we're at 5.19 now... (on arch... i don't expect manjaro to be more than 1-2 versions behind).I don't know what you used on kubuntu as i haven't used debian/ubuntu stuff for quite a while, but i'm pretty sure it's doable (with some time/work invested)... Or you have all the usual suspects (playonlinux, proton, lutris) for a more automated approach in the repos too.

The only thing pointless here is discussing with you, because the single one true thing you said is: "You cannot convince those people." Those people like you that can only repeat the same wrong stuff again and again. You don't even realize that those who talk about snowcrows only offering information are actually the nice ones that try to reason with you.But as you don't seem to bother actually reading the responses you might have missed the fact that most here aren't even that nice. They just tell you very directly how wrong you are. And they even give detailed explanations (not like you, who just talks random "facts" out of your ass then attacks people not agreeing).Seriously...You can't even write such an obvious troll post without showing that you have absolutely no clue and not even bothered to take a look at that evil website destroying raids or you might have noticed how a ranger using longbow is actually meta (with optional bonus points for knowing the difference between the suggested (optimized dps) moa and some (ferocious) bear is about ~800dps). Oh btw... that bear brings an 3sec invulnerability on a 40sec CD, which (unlike your fantastic ideas in this thread so far) can have a real use, for example ignoring mechanics at deimos. Ohh... wait... i forgot you don't care about real facts and probably know deimos only from videos that failed to explain to you why they are doing what they are doing anyway.

I just looked it up because it sounded strange that manjaro would use arch repos as a base to then remove the multilib repository. And at least the manjaro wiki lists core, extra, cummunity and multilib, exactly like arch does... Did they really remove those some time later and fail to change the wiki? :-o

Do i really read this correctly? You blame snowcrows for the fact that you saw a bad group that did not play their promoted team composition wipe multiple times? You must be kidding...

Say there's a competitive game with a dozen of different classes, with differing strenghts/weaknesses and playstyle. One player tests all the classes, looks at all the stats and realizes that class A is really strong and easy to play too, so he choses class A. The other one thinks about the meta game, knowing that many players will chose class A and that those made up nearly 80% of the last tournament (time for a nerf i guess^^), So he choses class M instead, which is rather weak overall but strong vs class A. He can now concentrate purely on practicing and developing tactics against the classes that are a bad matchup for him, knowing the majority of the matches will be easy wins. If you look at some pvp build on metabattle you will still find this idea in comments like "good build overall because it's strong version the heavily played build X, Y..." or "strong build but weak against build X, which is much more common since the last patch, so...". Or from a raiding perspective: Knowing not to play a phalanx strength warrior (which is a useful build by itself), because nearly every group brings 10-men might already. So the meta tells you to just bring banners for support while maximising your own dps.Knowing that the boon chrono nowadays plays Seize the Moment for quickness. Not because the quickness/alacrity buffing SoI builds got useless suddenly, but because the meta 10-men setup evolved. It changed from a double chrono setup to one subgroup playing firebrand/renegade instead to a setup with one alacrigade (or two condition renegades) with Righteous Rebel for raid-wide alacrity with either a chrono or firebrand provinding quickness for their subgroup.Or if i join a wing 4 pug run on my boonchrono, i should probably bring my dps gear/build for MO. Not because some website told me it's the best way to do it but because my knowledge of the playerbase tells me there will probably someone bringing his boonthief for quickness... And i will expect to being the tank at Deimos and plan for having some more thougness than the usual 1005. No, that's not what snowcrows' setup for Deimos tells me. That's knowing the meta or in this case knowing how most groups do the boss and that the most played handkite in pugs is a soulbeast build with 1380 thougness. (A build that you can find on the snowcrows website btw... allthough their own optimized composition is completely different)So no, the "Meta" is originally not at all about having the one most effective or easiest or whatever tactic. It's about knowing (beyond the useful builds in the game itself) how players usually do stuff, so you know what role you are expected to perform without having to discuss tactics/setups every single time you meet with others to kill a raidboss.

If there's any conclusion from the experience you seem to have while lfg-raiding it's that people who can't be bothered to invest even a single braincell into their gameplay but still think they should be successful in difficult content are toxic for the community. No amount of websites providing builds and guides (or complete lack of such sites) will change that in a meaningful way...

I guess you will have issues with every mmo running on badly configured amazon cloud servers.You just need to find someone other than anet who thought this to be a good idea... ;-D

You don't need a level 80 boost to get the raptor anyway. remember it's not a single player game ;-)