EVE Search - ATI Driver problems

All Channels

Linux

ATI Driver problems

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Pages: [1] 2 :: one page
Author	Thread Statistics \| Show CCP posts - 0 post(s)
Lothros Andastar Gallente	Posted - 2010.03.21 18:39:00 - [1] Can anyone tell me where I can find information to aid me in getting Eve working with Wine and ATI? Or do I need to stick in an nVidia Card? Is there any way of having 1 nVidia and 1 ATI Card in my PC and swapping between them?
Solbright Advanced Security And Asset Protection	Posted - 2010.03.26 00:55:00 - [2] Latest test result in the AppDB shows ATI card working. The important part appears to be... 2: Installed ATI catalyst 10.1 from binary file (10.2 has issues with Compiz and the game as well) 3:Didn't install ubuntu default ATI driver 4: Opened a terminal: regedit 5: Search for> hkey current user\Software\wine\Direct3D\ 6: Modify OffscreenRenderingMode to : backbuffer Presumably, the ATI driver is evolving fast and the default Ubuntu install is too out of date now. I don't recommend using winetricks d3dx9,d3dx10. Wine works fine now without those and those settings is what causes certain graphic glitching for me. Steps 10,11,12 are better fixed here - post #5. ----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up!
Solbright Advanced Security And Asset Protection	Posted - 2010.03.26 01:00:00 - [3] Opps, here's the test result in the AppDB - http://appdb.winehq.org/objectManager.php?sClass=version&iId=18563 ----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up!
Lothros Andastar Gallente	Posted - 2010.03.26 18:56:00 - [4] You sir are a gentleman! :D Eve now works absolutely perfectly except for: No Sound (Not an issue, never used it even on windowz) Slight Graphical Glitches (I didn't install Winetricks DX9 either :()
Solbright Advanced Security And Asset Protection	Posted - 2010.03.27 07:59:00 - [5] Good going there. Thanks for replying with your success. I guess the glitching is just the way it is then. I'm using a Geforce so there's bound to be differences. Questions: How hard was it to install the driver? Where did you get it from? ----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up!
Ravow Minmatar Cosmic Encounter	Posted - 2010.03.27 21:36:00 - [6] Edited by: Ravow on 27/03/2010 21:37:01 I have exactly the same problem with Catalyst 10.2, 10.3 and 10.4(available on gentoo-quebec overlay). Catalyst 10.1 don't have this problem(for me). But I stay with my 10.4 (I have upgraded to Xserver 1.8 so...) but putting the OffscreenRenderingMode to backbuffer fix the crashes!
Lothros Andastar Gallente	Posted - 2010.03.28 01:08:00 - [7] Originally by: Solbright Good going there. Thanks for replying with your success. I guess the glitching is just the way it is then. I'm using a Geforce so there's bound to be differences. Questions: How hard was it to install the driver? Where did you get it from? I got the driver from the ATI Site, I also used 10.1, as 10.3 didn't work. I am now however having a different problem. I have had to re-install Linux, and now my Prefs.ini is not "full", as in when it generates, there are only 3 lines clusterMode=LOCAL clusterName=LOCALHOST@NODOMAIN languageID=EN and eve then hangs on the splash, even if Wireless is disabled :( 2 Steps forward and 3 steps back
Solbright Advanced Security And Asset Protection	Posted - 2010.03.28 11:19:00 - [8] With the improvement for steps 10,11,12 there is no need for disabling the network. If you have an old backup of the cache and settings directories you could copy the prefs.ini from there. I've got a few of them stashed away, it's been quite handy to compare. Here's my current prefs.ini ... bitsCancelled=1 clusterMode=LOCAL clusterName=LOCALHOST@NODOMAIN debug=0 decimal=. digit=, eulaagreed=1 hdrEnabled=1 host=0 inputhost=localhost languageID=EN lodQuality=2 machoNet.acceptThreadCount=20 newbie=0 port=26000 rebootReason= rebootTime=129136878276585292 resourceCacheEnabled= shaderQuality=1 shadowsEnabled=0 textureQuality=1 ----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up!
Solbright Advanced Security And Asset Protection	Posted - 2010.03.28 12:05:00 - [9] Edited by: Solbright on 28/03/2010 12:07:27 I just did some googling and it seems what is being said is the opposite of what I presumed earlier - that 10.1 is actually an older release of the Radeon driver. The Ubuntu document on the subject talks about Catalyst 10.3 being the current default install for Ubuntu 9.10. ----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up!
Ben AdonKar Minmatar LifeLine Solutions	Posted - 2010.03.28 17:54:00 - [10] good stuff here! one thing l am not sure of though: Originally by: Lothros Andastar Originally by: Solbright Good going there. Thanks for replying with your success. I guess the glitching is just the way it is then. I'm using a Geforce so there's bound to be differences. Questions: How hard was it to install the driver? Where did you get it from? I got the driver from the ATI Site, I also used 10.1, as 10.3 didn't work. and Originally by: Ravow Edited by: Ravow on 27/03/2010 21:37:01 I have exactly the same problem with Catalyst 10.2, 10.3 and 10.4(available on gentoo-quebec overlay). Catalyst 10.1 don't have this problem(for me). But I stay with my 10.4 (I have upgraded to Xserver 1.8 so...) but putting the OffscreenRenderingMode to backbuffer fix the crashes! does this mean that 10.1 version of Catalyst in Lothros' case works only with backbuffer for ORM? and for Ravow fbo would also be fine? just curious. if this is the case and a cause could be found it would help others. ATI related posts are on the rise! personally l am using wine 1.1.37 with Catalyst 10.1 on Mandriva 2010.0. the glitches with backbuffer are definitely there. so changed to fbo. this gives rock stable performance as well. hardware is HD4670 in dual head mode with two WSXGA+ displays. if two clients are up this is enough to give an average framerate of 40+ fps for each one even in average w-space environment. xorg.conf had to be manually rewritten for dual head to work. initially l tried xinerama, which did not work out. xrandr was the way to go it seems. shader quality low, texture medium and LOD high. shadows are enabled. l do know that shadows are only implemented with shader on high. but the setting has some sort of impact otherwise. without this dual client does not run in a stable way. sometimes l got nightmares about this oddity ^^ maybe the fact that sound is enabled may be a natural explanation ... HKEY_CURRENT_USER\Software\Wine\Direct3D has the following keys (maybe more than actually needed): "DirectDrawRenderer"="opengl" "OffscreenRenderingMode"="fbo" "PixelShaderMode"="enabled" "VertexShaderMode"="hardware" "VideoMemorySize"="512" sound is possible with ati drivers as well. eve voice comes at a price: had to kick pulse, reconfigure alsa and make sure no sound daemon whatsoever is involved. also the need for taskset binding from each client to one cpu core may be related to use of sound. HKEY_CURRENT_USER\Software\Wine\DirectSound "DefaultSampleRate"="44100" "EmulDriver"="N" "HardwareAcceleration"="Full" have to use eve voice, mumble, mangler, and also teamspeak for what l do corpwise, so not much of a choice here. otherwise pulse would have been good! ________________________________________ the drowning man who climbs on your shoulders to save himself is understandable-except when you see it happen in the drawing room. dune
Lothros Andastar Gallente	Posted - 2010.03.28 19:38:00 - [11] Edited by: Lothros Andastar on 28/03/2010 19:39:04 Just tested fbo on my 5750 with 10.1 and Wine 1.1.41, and it's a non starter. Crashes on Jump as before.
Ravow Minmatar Cosmic Reserve	Posted - 2010.03.29 17:07:00 - [12] I used 10.1+Wine 1.1.37 with fbo mode for long time without problem (I tried 10.2 and reverted back...) But now I switched to 10.4 and Wine 1.1.41+backbuffer. I got the backbuffer glitch but I don't get any full system crash* anymore and I can use a "instable(normal version for me)" Xserver. * Append in random time when I use fglrx < 10.4 (on desktop, on EVE, when I do some web surfing...)
Ben AdonKar Minmatar LifeLine Solutions	Posted - 2010.03.31 18:41:00 - [13] thx a lot for clarification! one thing that strikes me is that the test hardware on the appdb link given above had the same series of card as the one used by Lothros, 57xx. in both cases fbo as ORM seems to lead to crashes. only backbuffer working. l would have gone for a cpu related issue. but afaik the taskset option only is needed for AMD dual core cpus. the tester at appdb uses Intel Core I5. if anybody new to wine wants to make sure: just use 'taskset -c 0' as a prefix to your usual start command in terminal or start icon. (without the ') taskset -c 0 env WINEPREFIX="/home/user/.wine/" wine explorer /desktop=0,XxY "C:\Program Files\CCP\EVE\eve.exe" above line would be a minimal version for starting up. before you should run winetricks or winecfg once to create the folder needed for env. X and Y apply to resolution, user is the path to your ~ directory. as solbright pointed out in this thread, posts 4 and 5 it has also drawbacks to limit the client to one core. correct me if l am wrong, but if the client is limited to one core in windows natively it seems to be a huge advantage to be able running it with two cores by means of wine. apparently the factor that makes an impact is the extra cpu power in situations generating load. limit it to one core and watch the fps graph when jumping at a gate or rendering with the in game browser. depending on your cpu clock per core the impact can be significant. l would love to take advantage of being able to run two cores. it just is not stable on my AMD dual core, alas. see non deterministic cpu architecture for a general idea of dual core impact when it comes to software development. ________________________________________ the drowning man who climbs on your shoulders to save himself is understandable-except when you see it happen in the drawing room. dune
Solbright Advanced Security And Asset Protection	Posted - 2010.04.01 02:01:00 - [14] I'm using an Athlon64_X2 @3400MHz and it's rock solid without using taskset. So, it's not your multi-core CPU causing the crashes. IMHO, finger is pointing at either sound or 3D drivers. ----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up!
Solbright Advanced Security And Asset Protection	Posted - 2010.04.01 02:14:00 - [15] Edited by: Solbright on 01/04/2010 02:15:54 PS: The article linked has Lewis Page being dumb by mixing two independent problems together where he says: "... where changes in wire temperature or other hard-to-predict shifts can alter the sequence in which information arrives and gets processed - can be a nightmare." Hardware timings are a hardware problem. General computing software, and certainly not apps, should never have to contend with such glitches. The 'concurrency bugs' that Luis Ceze is talking about is a software design issue that coding jockeys should always be aware of but can become problematic so he's promoting their debugging software as the savior. ----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up!
Solbright Advanced Security And Asset Protection	Posted - 2010.04.05 03:52:00 - [16] Hmm, it's looks like Lewis Page was suckered. Having now read some of the other press releases it appears SAMPA are obfuscating to cover every possible base, and get lots of inquiries presumably. I think I'd hate being a tech journalist. Press releases would wind me up too much. I can almost see the editor breathing down my neck already - They pay our bills you know!
Ben AdonKar Minmatar LifeLine Solutions	Posted - 2010.04.18 04:29:00 - [17] Originally by: Solbright I'm using an Athlon64_X2 @3400MHz and it's rock solid without using taskset. So, it's not your multi-core CPU causing the crashes. IMHO, finger is pointing at either sound or 3D drivers. thx for this! so definitely AMD dual cores are running without limitations. it might still be hardware related, like some types need the option or some CPUs (like mine ) are faulty. might be bios as well. have given no thought to sound and drivers before, but l will definitely do some more testing now. maybe after kicking pulse l had overlooked a sound daemon still running in the background? ________________________________________ the drowning man who climbs on your shoulders to save himself is understandable-except when you see it happen in the drawing room. dune
Ben AdonKar Minmatar LifeLine Solutions	Posted - 2010.04.18 04:35:00 - [18] Originally by: Solbright Edited by: Solbright on 01/04/2010 02:15:54 PS: The article linked has Lewis Page being dumb by mixing two independent problems together where he says: "... where changes in wire temperature or other hard-to-predict shifts can alter the sequence in which information arrives and gets processed - can be a nightmare." Hardware timings are a hardware problem. General computing software, and certainly not apps, should never have to contend with such glitches. The 'concurrency bugs' that Luis Ceze is talking about is a software design issue that coding jockeys should always be aware of but can become problematic so he's promoting their debugging software as the savior. Originally by: Solbright Hmm, it's looks like Lewis Page was suckered. Having now read some of the other press releases it appears SAMPA are obfuscating to cover every possible base, and get lots of inquiries presumably. I think I'd hate being a tech journalist. Press releases would wind me up too much. I can almost see the editor breathing down my neck already - They pay our bills you know! true. tech journalist implies expertise in two fields the way l see it. more or less the best results seem to come from environments with lots of feedback. either in a highly efficient and linked team of writers, from reader responses or both. in this particular case the team of SAMPA were successful creating global coverage of their Jinx debugger. quite impressive. next to bills getting payed l could also think of individual reasons for the involved writers. if the topic is covered this way they improve their standings with the corporation so to speak if their social network is big enough and standings are good they could rely on anything from support to insider informations. keeping the balance between these factors and being as objective as possible for readers' benefit is part of what makes any good journalist the way l see it. an other part of it may be workload. if someone provides info and support to journalists in a highly efficient way this might improve their presence. something many journalists seem to like is cross reference. which lead one of them to get in touch with a researcher participating in PEPPHER project . l didn't pay as much attention as you did, but as you mention it the hardware claim seems odd. wondering whether debuggers like this one can also provide help in finding hardware errors. as you wrote, this claim in itself is highly obfuscating. the best definition l have found so far is this: Wikipedia Article on Jinx Debugger Valgrind with ThreadSanitizer may fall into this category? all of this comes back to ATI Driver problems. given the fact, that many of us also are using multi core cpus we have to deal with layers consisting of e.g. hardware, bios and the likes, os, drivers, x-server with wms and gdms, wine, EVE client. settings and caches are a consideration as well. what happens for instance if the CPU starts working parallel and one of the elements listed above does not support this? Deadlocks, Race conditions and all Unusual software bugs in general are lurking along the way to starting up EVE one of the strangest bugs l ever heard of was a tinfoil-style, crappy tower whose vibrating fans caused slack joints given the load of factors it may be crucial to eliminate as many other sources of failure as possible before dealing with the ATI drivers. l will try giving more information in case it is not working yet. guess most is for beginners, but maybe users from intermediate level up can find a hint or two as well. same goes for proprietary operating systems. ________________________________________ the drowning man who climbs on your shoulders to save himself is understandable-except when you see it happen in the drawing room. dune
Ben AdonKar Minmatar LifeLine Solutions	Posted - 2010.04.18 04:42:00 - [19] general rules for building a good rig: column system, making sure everything works step by step. Hardware: buy smart! cheapest quality ftw. read on hardware sites for this! either avoid noise and heat from the beginning. or use a tower built for noise reduction, generally employing 120mm fans to shovel heat out efficiently. l prefer the first method (energy efficient!), other one is the only option for high end gear. for linux always check driver support before buying any hardware. use RAMs on the QVL only, if not possible use similar DIMMs as the ones on the list. if you don't know what you are doing: don't mix modules! buy all the ones you need right at the start, if you have to upgrade use only the same type. 2 gig are good, going multiple client 4 Gigabyte are better. check it, test it. if you are sure everything is good start booting from a live medium. make sure temperatures are fine. for this purpose and all subsequent tests l do recommend grml. BIOS, OFW, or coreboot: set it up properly. take your time, make sure you understand what you are doing. otherwise get help. or set to defaults. overclocking, undervolting and the likes are only for experts. in some rare cases just this may be necessary to get the whole thing stable though. test it: once everything is set the time for a stress test has come. use Memtest86 or + version. cpuburn and the likes should also be used. memtest alone would not cover all possible glitches. if you can run memtest for one full cycle and cpuburn on each core simultaneously for circa an hour you should be good. to be 100% sure you have to run each for at least a day, alas. in any case use a voltage/rpm/temperature monitor of your liking, e.g. gkrellm. to use it lm-sensors' sensors-detect command should be applied. if you have trouble implementing this from the grml medium you can also use it for initial tests and run the 24h+ one from the already installed distro: More Hardware related stuff: before installing any modern os you should check your internet connection from the computer you are working on. in regards to EVE and gaming in general it should have low latency. under 100ms ping times are ok for everything. if higher it is game dependent. packet loss should be close to 0% average, packet delay variation ('jitter') as low as possible, throughput/goodput may not be so important for gaming. few kilobits per second and client mostly. same for EVE. but for installing the os (d/l, update) and multimedia it can never be high enough in any case, eve under wine is very finicky when it comes to network quality. failure here might well cause errors described in my posting above! partitioning is also crucial. different partitions do have different read and write speeds. and again eve under wine is touchy. therefore the directory in which eve is installed should be one with very high read and write speeds. this will make it more stable aside from the boost! one setup may be swap-main-home>(with wine). check smartmontools, hdparm and hddtemp for further info on hds. Drivers: according to above posts right now you can either try fglrx 10.1 with fbo. or play it safe and use fglrx 10.3 with backbuffer. sound should be muted. you can try to enable it later on, if you need it desperately getting rid of pulse audio might help. packages are not always the same. in mandriva 2010.0 there is a bug preventing you from installing the fglrx 10.1 driver from the ATI site installer. included package is flawed. the 10.1 repository package (from the same maintainer!) installs like a charm. same is true for ubuntu: some driver packages are good from ATI, others from repo. in some cases the entire funcionality of the graphical interface can depend on this! Install: only if everything works you can d/l and install EVE properly! Phyton: CRUCIAL! using 2.6 here. ________________________________________ the drowning man who climbs on your shoulders to save himself is understandable-except when you see it happen in the drawing room. dune
Ben AdonKar Minmatar LifeLine Solutions	Posted - 2010.04.18 05:04:00 - [20] Edited by: Ben AdonKar on 18/04/2010 05:04:03 Drivers: according to above posts right now you can either try fglrx 10.1 with fbo. or play it safe and use fglrx 10.3 with backbuffer. sound should be muted. you can try to enable it later on, if you need it desperately getting rid of pulse audio might help. packages are not always the same. in mandriva 2010.0 there is a bug preventing you from installing the fglrx 10.1 driver from the ATI site installer. included package is flawed. the 10.1 repository package (from the same maintainer!) installs like a charm. same is true for ubuntu: some driver packages are good from ATI, others from repo. in some cases the entire funcionality of the graphical interface can depend on this! Install: only if everything works you can d/l and install EVE properly! Phyton: CRUCIAL! using 2.6.4 here. 2.4 was fubar. anybody got experience with 3.0? ________________________________________ the drowning man who climbs on your shoulders to save himself is understandable-except when you see it happen in the drawing room. dune
Ravow Minmatar Cosmic Encounter	Posted - 2010.04.21 15:00:00 - [21] Want to add something about fglrx > 10.1 with backbuffer: - Probes and POS object became not movable after a variable time of utilizations (usually less than 30 seconds). This is very... annoying especially when you need to find a wormhole or probe for a customer. I tested with fbo and the problem is not here (I can play with them all day long, no problem... Except when I jump and got a access protection error thing! Someone have the same problem with backbuffer? Or a way to bypass it, other than loop{ restart client in fbo... probe, restart the client in backbuffer... jump}?
Blank Protection State War Academy	Posted - 2010.04.22 09:48:00 - [22] There are way to many combinations to get Eve work under Linux. I still have very basic hardware and it took me a lot of time to get it work. Found out that this was the best configuration for an AMD 64 bit, ATI Radeon HD3870 system with 3 Gb Ram. You always can just do the following what i did. 1) Install Ubuntu 9.10 64bit ( 34 version ) version. 2) Manual download and install Wine 1.1.40 ( later version didnt even start Eve on my system. 3) Install Play on Linux ( also with the packet installer ) 4) Install Winetricks and choose all in the below list to install: Corefonts d3dx9 Allfonts ddr=opengl glsl-enable multisampling=enabled orm=backbuffer rtlm=auto You can choose and install them all in ones and choosing this option you dont need to messing arround in the registry because its been configurate automaticly by Winetricks. So far for the linux part. Now the ATI driver. For me the Catalyst 10.1 driver is stil the best and i can even go back to the older Catalyst 9.3 version. Both are working fine but be aware i have a ATI Radeon HD 3870 card. So all newer ATI cards should stick with the 10.1 driver till the linux Ubuntu 10.4 is ready to go. Even the commercial FGLRX from ATI/AMD that comes with the packet installer should work fine tbh. So far for the ATI driver`s installation. Editing the pref.ini file This is the most simple part. Just go to or find the pref.ini file in the settings folder of you Eve directory and copy/past this: clusterMode=LOCAL clusterName=LOCALHOST@NODOMAIN debug=0 decimal=. digit=, eulaagreed=0 host=0 inputhost=localhost languageID=NL machoNet.acceptThreadCount=20 newbie=0 port=3724 You see the "bitcancelled=0 or 1"part is gone. Thats because you dont need it in linux at all. Make the pref.ini file read only and you are ready. Wine configuration Go to application--> Wine--> Configure Wine-->Graphics Tab. Than click all option but not the one with the DirectX option in it,leaf it open. Than set your Desktop resolution to your choose. I have it set to 1680 X 1050 because i run 2 clients in the same desktop envirment. No you ready to go to play Eve on your Linux machine. Be aware of the test information/configuration on the WineHQ website. It says that EVE has Gold under Wine 1.1.43 but all the discription en testing is been done under Wine 1.1.41. And the configuration isnt up to dat anymore. Lot what i have been written here is already been said but some extra always helps i hope. Good luck. This Post belongs in Out of Pod Experience
Ben AdonKar Minmatar LifeLine Solutions	Posted - 2010.04.24 04:28:00 - [23] Edited by: Ben AdonKar on 24/04/2010 04:37:43 Originally by: Ravow Want to add something about fglrx > 10.1 with backbuffer: - Probes and POS object became not movable after a variable time of utilizations (usually less than 30 seconds). This is very... annoying especially when you need to find a wormhole or probe for a customer. I tested with fbo and the problem is not here (I can play with them all day long, no problem... Except when I jump and got a access protection error thing! Someone have the same problem with backbuffer? Or a way to bypass it, other than loop{ restart client in fbo... probe, restart the client in backbuffer... jump}? confirming this behaviour on fglrx 10.1 under wine 1.1.37 as well. same problem here l guess l somehow had suspected that your probe trouble is related to the mining turret fps drop so l followed the solution described above and set HKEY_CURRENT_USER\Software\Wine\Direct3D\UseGLSL to disabled while using backbuffer. it did not fix the problem. at least not always ... in some runs l succeeded in probing for a prolonged time. once it got over a certain point it would go on for the entire run. l scanned down a WH without any trouble this way. not sure if this phenomenon is triggered randomly or if there is a general way to overcome it. like moving all probes quickly, changing scan radius and doing one scan before the actual stalling occurs. if the latter is possible, it might not be related to the UseGLSL key at all. maybe a dozen runs were not enough to succeed with UseGLSL enabled. in any case it might provide results to debug the whole thing and compare the difference between the two settings. the only other thing l can possibly think of would be a test if you can do your session change employing the taskset option in eve startup line. this way you could run fbo. l have chosen just this combination, the only way to use probes and jump glitch free atm. but Solbright suggested it could also be sound related. so l am not sure at all about this. looking forward to doing some more tests regarding sound. ________________________________________ the drowning man who climbs on your shoulders to save himself is understandable-except when you see it happen in the drawing room. dune
Solbright Advanced Security And Asset Protection	Posted - 2010.04.24 06:27:00 - [24] The sound suggestion was only for crashes soon after startup or sitting idle in station or similar unexplained crashes. I can't see the probing problems being anything to do with sound. ----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up!
Ben AdonKar Minmatar LifeLine Solutions	Posted - 2010.04.24 07:35:00 - [25] Originally by: Solbright The sound suggestion was only for crashes soon after startup or sitting idle in station or similar unexplained crashes. I can't see the probing problems being anything to do with sound. just to clarify this, the probing itself goes perfect with fbo. the crashes without taskset are happening mostly when changing session. no matter if this session change occurs at a stargate or a station. in any case cpu-load is high and sound involved. but as l said not sure about it. the only way to find out will be running some tests, planning on doing that, hopefully in the next couple of days. ________________________________________ the drowning man who climbs on your shoulders to save himself is understandable-except when you see it happen in the drawing room. dune
Mobius Chimera	Posted - 2010.05.22 09:06:00 - [26] FYI, none of this is fixed with wine 1.2-rc1, released today. Flashing and stalls with Catalyst 10.4 driver are unchanged.
Mr M Legion of Illuminated Social Rejects	Posted - 2010.05.30 04:37:00 - [27] Hmm... I'm running wine 1.1.42 and the new catalyst 10.5 drivers and it seems like fbo works again. Eve loads, it looks like it renders right and I can move probes. Haven't done any winetricks here except for the fonts. Eve Tribune\|EVEgeek\|Firebrand Radio
The MeatGrinder	Posted - 2010.05.30 07:20:00 - [28] Edited by: The MeatGrinder on 30/05/2010 07:20:52 I've tried wine 1.1.42, 1.2rc1, and 1.2rc2 with catalyst 10.4 and 10.5, and all of them render messed up (unusable) colors on all menus after clicking on the audio tab in settings. Additionally the 4 lights on the ship on the login screen in tyranis are also fubar. Additionally, I cannot load the station environment even with Jukebox renamed and sound disabled! It hangs X. I've tried all of the registry settings I could find on the forums in different combinations... Is anyone else running ubuntu 10.04 x86_64 with a 58xx series card successfully? Share the knowledge!
Lothros Andastar Gallente	Posted - 2010.05.30 08:31:00 - [29] Edited by: Lothros Andastar on 30/05/2010 08:33:04 I've tried wine 1.1.42, 1.2rc1, and 1.2rc2 with catalyst 10.4 and 10.5, and all of them render messed up (unusable) colors on all 2D surfaces (menus, chat windows, etc) after clicking on the audio tab in settings or by simply logging in. Additionally the 4 lights on the ship on the login screen in tyranis are also similarly fubar. Additionally, I cannot load the station environment even with Jukebox renamed and sound disabled! It hangs X. I've tried all of the registry settings I could find on the forums in different combinations... Is anyone else running ubuntu 10.04 x86_64 with proprietary drivers for a 58xx series card successfully? Share the knowledge! Heya. I'm running a 5750, Catalyst 10.4 and Mint 9, so this might not help at all, but here goes. 1) Create a separate wine prefix for eve by typing in: WINEPREFIX=~/.DESIREDFOLDERNAME winecfg 2) In the config that opened, make sure to disable all sound codecs (IMPORTANT, yes it sucks but thats life )and to set it to emulate a virtual desktop equal to the size of your screen 3) Use winetricks to set the following Corefonts ddr=opengl multisampling=disabled orm=backbuffer rtlm=auto 4) Install eve by typing: WINEPREFIX="$HOME/.DESIREDFOLDERNAME" wine 'path to installer' Tip: 'path to installer' can be easily done by draging and dropping the installer after you type the first bit 5) Make a sandwich while it installs. 6) Load up eve, disable sound, login, disable eve voice (IMPORTANT) then click a character. Should work fine from then on out. For alts, make a new wine prefix again to prevent cache corruption errors and crashes.
The MeatGrinder	Posted - 2010.05.30 15:15:00 - [30] Edited by: The MeatGrinder on 30/05/2010 15:19:27 I've done all that, except that I don't do the wineprefix, because I have no other profiles to care about under wine.

Pages: [1] 2 :: one page
First page \| Previous page \| Next page \| Last page

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.