Morcant
-
Posts
335 -
Joined
-
Last visited
Posts posted by Morcant
-
-
also I get these messages whenever I do winetricks, its a warrning that I am running in 64bit and if I'm experiencing issues, to reset it in a clean 32bit. is that my problem? and if so how do I make it into a 32bit version?
Yes, that is most likely your problem. 64-bit wine is an unholy mess. You need to uninstall wine, and reinstall with the 32-bit package, even if your system/OS is 64-bit.
-
its ok, Its awsome I'm getting to learn this stuff
it worked, but now it is getting to say the update for directx failed, so what I tried to do was go to winetricks, is that the right way to go? and if so what components to I need? when I tried installing directx components it said this
d3dx9 install completed, but installed file /home/edgar/.local/share/wineprefixes/steam/dosdevices/c:/windows/system32/d3dx9_43.dll not found
Winetricks is what you need, yes. What command did you use?
WINEPREFIX=/home/edgar/.local/share/wineprefixes/steam winetricks d3dx9
is all I've ever needed to do.
-
now how do I manually replace the Launcher.exe. the launcher.exe.tmp?
Sorry for getting back to you so late. To replace the file, you can do it in a GUI file manager by simply deleting Launcher.exe and renaming Launcher.exe.tmp to Launcher.exe, or on the command line
rm Launcher.exe
mv Launcher.exe.tmp Launcher.exe
-
the issue is when I got to my C: in wine and than program files(x86) there is no steam folder, what do I do?
Find the shortcut you're using to launch Steam, check its properties, and use that to locate your missing Steam folder, because it obviously exists somewhere.
-
thing is I cant find the directory for it. I went into .wine/ than C:/ than Program Files(x86) but I cant see a steam folder.
I can actually find it in c:/ users Edger/(mycomputer name) Application data/ warframe/ downloaded/ public/ tools
is this it?
If you're using the standalone install, then yes, it is stored in that directory.
If you're running the Steam version via Wine, the launcher should be stored in steamapps/common/Warframe/Tools.
-
ok so I have ubuntu 14.04 and I am relativly new to linux. I've downloaded wine and tried this through steam. and I got a white screen and the highlightable text here
Uptate failed!
Could not update file:
C:\Program Files (x86)\Steam\SteamApps\commo\warframe\Tools\Launcher.exe
Files not found. [0x00000002]
I'm really thinking this is an easy fix but I'm lost at how to make this thing find the correct file. what do I do here?
You have to manually replace the Launcher.exe file with the Launcher.exe.tmp that was downloaded in the same directory, then launch it again.
-
Anyway, people in this thread seem to have Warframe running relatively smoothly on lower-end hardware, so I'm going to have to ask you for your secrets.
I've turned all the settings down to a minimum, and my FPS seems to be above 100 most of the time, yet I'm getting heavy fps lag spikes constantly, both in the menus and in-mission. I was able to run around the dojo and everything looked the same as on Windows, but the lag spikes persisted, both with and without virtual desktop.I'm playing in fullscreen but windowed seemed to have the same issue.Does anyone experience the same and/or have a solution?Try using Wine version 1.7.13. 1.7.14 introduced a nasty graphics regression, and as far as I know the fix hasn't been merged into the main development branch. Discussion on WIneHQ Bugzilla here: http://bugs.winehq.org/show_bug.cgi?id=35718
-
I came to the forum to make the same complaint. The Mob Def missions are slow and boring.
Same map (which is absolutely terrible for mobile defense, by the way)
Fewer enemies, virtually no specters
Forced 2+ minute wait per terminal
No amount of battle pay is worth enduring this. People aren't going to play these.
Why does DE hate going fast?
-
How is the performance under linux? I run several flavors and am curious. I may give this a try though I mainly play from a windows workstation (game machine) but if it runs well in wine, well I would prefer not to run windows if I can help it.
In my experience, approximately 66% of Windows performance on a i5 3570K and Radeon HD 7950. I get between 30 and 80 fps in missions, generally, depending on envvironment and enemy density, dips of similar scale are evident on Windows 7 as well. Debian testing got a couple relevant updates just before I left town, so I'll test more when I have a chance to see if there's any improvement.
-
Was this act of banding together to fight off Alliances who intend to use tax going to become the TREND?
Not for TREND. Not for CORPORATE ATTITUDE. Not for STONER. Only true DOOM-MURDER HEADS.
-
Given Eclipse can still afford to pay 40k per run in the future, or potentially more given they aren't constantly bombarded by the angry mobs...
The community could easily make double or tripple that 40k in the same 5 minute time span.
This damage control.
Battle pay is inconsequential. It's available until the moment Eclipse is assured victory, then abandoned. A supply of credits offered for such a brief window does not in any way excuse Eclipse's ever-increasing and already egregious tax rates over the following two to three days of armistice.
That battle pay is changed on a whim compounds the issue, making it a very unreliable and high-risk bet for players. Even if battle pay exceeded losses to taxation (it doesn't), a Dark Sector with low/no tax is a more consistent and reliable credit farm, available the majority of the time regardless of conflicts.
The more property a single Alliance/Clan owns the less they would need for higher tributesAnd this is simply disingenuous. Eclipse have demonstrated by their actions that holding the most nodes of any clan or alliance has led only to higher taxes. Talk is cheap; players can see clearly what has become of misplaced faith in such promises.
-
I ran missions with pugs nonstop for the first hour and a half or so before I had to bow out when Eclipse was at 20%. I sacrificed half a night's sleep between Sechura and Gabii, but it was my pleasure to do so. Thanks for honoring your commitment, Shadows of Vengeance. I'll be there to assist in future battles.
-
I am sorry but what do you mean? I really do not understand this sentence.
Arrr thanks, i think he misunderstood what i was trying to say.
He was responding to the fellow named Terry3373 a few posts earlier in the thread regarding frustration with being unable to deploy a rail. It had nothing to do with what you said.
-
I seem to recall them upping the battle pay up to 60k there at one point. And still getting stomped.
The battle for Ceres - Gabii was even more interesting - players have reported seeing 200k battle pay.
I can vouch for that. I received one of those from TW Alliance about 1/3 or 1/2 way through. I thought someone must have misplaced a zero.
-
Looks like enough people remembered how dark sectors work and ran against Eclipse which actually accomplished what they wanted where whining on the forums didn't, and the sector is still held by the people it was previously held by.
Implying that the "whining" on the forums wasn't an integral part of mobilizing an unorganized resistance. Propaganda works both ways.
By raising awareness and educating people on the value of lower tax versus higher battle pay, Eclipse was not just defeated, they were demolished. Their morale was so low following Gabii they barely even participated for Sechura.
-
Both are greedy in their own way, and that has been my point during this entire thread. I never once called Eclipse *not* greedy.
My point has always been "You can't call Eclipse greedy when you're greedy yourself".
Eclipse wants to move in and tax the rail. Yes, that's greed. That's the obvious part I left out, because... well, that's Obvious.
People supporting SoV want to keep all the money to themselves, so they demonize Eclipse and call them Greedy. The problem is, you can't call them greedy without admitting to your own greed, right?
I support free and low-tax rails. Up to 10% is reasonable. I'd give half my earnings to free rails if the option were present.
But personal motivations are really beside the point. Players running missions are earning that reward, and taxation demands a cut. What has any rail host done to earn the tax revenue they are collecting? In many cases, they were simply the first to click "deploy". Inertia and a pittance of their wealth doled out to entice unaffiliated Tenno ensures they stay in control. I don't find that particularly laudable or worthy of a share of my mission reward -- certainly not a quarter of it.
-
More Tax = More Battlepay.
More tax = more tax. Battle pay changes at Eclipse's whim. High at the beginning, then meager, then none as they grow more and more secure in victory. If you miss the first 20 minutes of a conflict, you get table scraps if anything at all.
Their tax remains high regardless of circumstance, and as we see now, it's simply being used to fuel expansion while they play victim and cite maintenance costs to people who don't know better.
Don't believe their lies.
-
After further research they found out that the tax does NOT take away the end game credit reward but instead takes the ones you earn in the missions, let's say you get 100 credits from enemies eclipse would take 5% of that. So 5 credits. So they raised it to 25 seeing as it has little to no harm, and it's been like that ever since.
Propaganda machine is running at full tilt, I see.
-
I value free Dark Sector rails quite highly, but there is presently no practical avenue for me to choose to support them, aside from mobilizing friends against attackers. I would like to see a UI option to donate a percentage of my credits/resources to the rails I use, whether they are taxed or not. Would this be a feasible addition? Would other players use it? Feel free to comment with ideas or criticisms.
-
So assuming a full load of 23K per run, I'd make 17,250 per run of that and if there's a 25% tax on that (it's listed as 15% right now though) then Eclipse would get 5,750 credits.
Which is still below the pay rate for the conflicts I bother to run, so I still come out way on top in credit gain compared to Eclipse. And as long as the tax rate is 49% or below, I will continue to earn more credits than Eclipse does per run, not even factoring in if I take any of their battle pay.
Let me rephrase what you just said for clarity.
"As long as I get to keep the slimmest majority of the money I'm earning by actually running the mission, I'm cool with it.
I'm fine with taking 51% of my earnings while giving the rest to the tax authority in exchange for nothing of value."
Holy S#&$.
-
Players ignore the taxes because they never see the money they're losing. It's very transparent, and the propaganda in this thread is tuned to this very fact.
But players always take notice of fat battle pay rewards, which cycles into Eclipse winning every conflict and getting more and more tax revenue to fuel expansion.
Thus, Eclipse will continue to grow until they swallow the whole system, all while spouting platitudes of non-aggression.When taxes hit 50%, will you care then? How far is too far? Remember, peacetime is tax time, and it's now a minimum of 4 times longer than conflict.
-
Nice guide here, I recently switched from windows to zorin (which to my understanding is like a reskin of ubuntu?) and liking it a whole lot better. Followed this guide to try and get warframe working on it, though I'm having some trouble.
The launcher launches, and even patches, but it patches forever. It keeps cycling through different patches that have enormous sizes (maybe 44-5 different ones ranging from 2000 - 7000 megabytes) and it never stops. I'm certain I remember warframe not taking up that much space on windows, but I'm also wondering is it something else causing that?
Same issue here, the launcher downloads infinitely with Bad LZMA stream and LzmaDec_Allocate failed errors in the log.
While mucking about, I accidentally deleted my Cache.Windows folder contents, so I just had to face this issue myself. You can resolve this one of two ways. Run the download in Windows, then copy or symlink Cache.Windows to wherever your Wine Warframe installation expects it to be. Or you can use Steam (via Wine, not Linux-native Steam) to download the game, and do the same thing. Not sure if it runs properly through Wine Steam, but aside from the Steam overlay I don't see why it wouldn't. That would save the hassle of copying/linking.
I'm not sure why the standalone installer fails repeatedly with LZMA-related errors while Steam works perfectly. But at least the Steam repository has been updated to a more recent version of the game (dated sometime in April).
-
I go to break some crates, open some boxes before exiting. My screen goes black, my monitor is no longer 'connected' to my computer. All sound turns off. I must force my computer off.
Highly speculative, but this sounds like a power supply issue. Perhaps an old PSU where capacitor aging has diminished its ability to supply adequate current to meet the GPU's high demands.
Most other failures (in the game code, driver, Windows) behave differently and fail somewhat gracefully. Even a hard GPU lockup will freeze/blank the screen with the audio looping, typically, unless perhaps you're using the integrated HDMI audio of newer cards.
Difficult to test without another PSU to try, and if the interval between occurrence is a month it will be very hard to confirm. But that's my theory.
The network problem is probably a side effect and should be resolved by correcting the primary issue, whatever it ends up being.
-
I'm getting constant driver failure and WAR-223449 with my GTX 660. I never have any issues with anything else.
Just verified local files and it said 117 need to be redownloaded, 4.2 GB... guess thats the whole game.
Warframe patches independently of the Steam content distribution. You're effectively rolling back to a prior Warframe version, which the WF launcher will then have to re-patch. If you're going to verify, use the WF launcher. Click the cog icon in the upper right corner, then the Verify button below Download Cache.
[Guide] Warframe On Linux With Wine
in Players helping Players
Posted
Sounds identical to the issue I experienced when a nasty regression found its way into wine's d3d component. If you're okay with compiling wine, you could try patch 48503 from https://bugs.winehq.org/show_bug.cgi?id=35718 which should apply to wine source up to version 1.7.25. There are modified versions later in that comment thread for version 1.7.26 and 1.7.27. If you're not okay compiling wine, use version <= 1.7.13, since the issue was introduced with 1.7.14.
Just tested with the latest wine-git, it hasn't been fixed there yet, so who knows when the fix will work its way into numbered releases. 1.7.27 works fine with the modified patch (attachment 49679) from the thread linked above.