Pages: 1 2 3 4 [5] 6 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 17 post(s) |
|
CCP Gangleri
Minmatar
|
Posted - 2008.12.17 20:17:00 -
[121]
Edited by: CCP Gangleri on 17/12/2008 20:19:29
Originally by: Roan Keltizar Hey, I just wanted to submit my bug/suggestion report. Take it or leave it. Just thought the EVE team would find it helpful.
1. You need to select the structure and activate it either via the "selected item" interface or by right clicking it. It may help to hover over the icon to separate the gate from the beacon as they are sometimes quite close.
2. I assume you are talking about how your ship will jump back a little when coming out of warp, not a bug.
3. Re-arranging planets to optimise a solarsystem to have no planets in the most used warp paths would probably not produce very believeable solarsystem layouts
4. The sound effect is not meant to be anything like an evil laughter.
5. You can sell a ship, but there may not be anyone buying that type of ship. Eve has a player driven market, only a small percentage of market items are NPC trade.
6. I'm not sure what you are asking for here.
7. Going faster and faster into infinity would not be feasible for gameplay purposes.
8. It is quite easy to reduce your speed manually to achieve this, I'm pretty sure we would not be able to create a system that could correctly fulfill your expectations for this.
9. Hold down CTRL and click the target, either on your overview or the icon in space.
10. No.
edit: This part of the forums is meant to help out newer players with questions like these. EVE New Citizen Q&A ------------------
|
|
|
CCP Atropos
C C P
|
Posted - 2008.12.17 20:35:00 -
[122]
Originally by: SSgt Sniper poasting to confirm minor cap bugs on setups that used to be more than cap stable. Currently, most of them still are, but barely. One or two are no longer stable.
Investigate!
Are they actually cap unstable or does it appear unstable when you watch the cap bars on the Neocom?
|
|
Erin Grekka
Minmatar Intaki Peace
|
Posted - 2008.12.17 21:51:00 -
[123]
Patched the client yesterday, logged in and sat in a station for a couple of hours. Had no problems. Logged out and put PC on standby. Today I try to start Eve and get 'Your EVE client installation may have modified, damaged or corrupt files. Please re-install the game client Verification failed: "...\EVE\bin\_trinity.dll", crc:8d8746ab, expected:bfdf9214.' Removing the cache made no difference (although it did free up 150 Mb of old patch files and machonet files.
I will try again with logserver and bugreport. Hopefully this doesn't happen every time I close Eve. |
Par'Gellen
Gallente The Scope
|
Posted - 2008.12.17 23:45:00 -
[124]
Whatever you guys did at DT this morning fixed my cap issues. I'm back to cap stable at 50-ish percent. Thanks! ---
To err is human. But it shouldn't be the company motto... |
Erin Grekka
Minmatar Intaki Peace
|
Posted - 2008.12.18 02:16:00 -
[125]
Originally by: Erin Grekka Patched the client yesterday, logged in and sat in a station for a couple of hours. Had no problems. Logged out and put PC on standby. Today I try to start Eve and get 'Your EVE client installation may have modified, damaged or corrupt files. Please re-install the game client Verification failed: "...\EVE\bin\_trinity.dll", crc:8d8746ab, expected:bfdf9214.' Removing the cache made no difference (although it did free up 150 Mb of old patch files and machonet files.
Problem fixed with a reboot. I didn't see any mention of a reboot needed when the patch was applied. It's also not particularly practical to have to reboot just to patch Eve so I hope this isn't going to be common in future. |
MMXMMX
Caldari Resistance is Futile
|
Posted - 2008.12.18 02:37:00 -
[126]
Originally by: Par'Gellen Whatever you guys did at DT this morning fixed my cap issues. I'm back to cap stable at 50-ish percent. Thanks!
Yes same here all cap problems are gone
Its working fine again thanks CCP
|
The Vixen
|
Posted - 2008.12.18 05:04:00 -
[127]
I'm interested to hear what the problem was.
|
Pedronicus
Caldari Phantom Armada
|
Posted - 2008.12.18 05:13:00 -
[128]
Posting to confirm that cap issues on my ships are back to normal yesterday after downtime. something was wrong there and that is corrected now, if CCP finds out what was wrong that could prevent such problems from occurring in future. -------------------------------------------------- Holiness is in right action, and courage on behalf of those who cannot defend themselves. |
Ravenja
|
Posted - 2008.12.18 11:31:00 -
[129]
Yup, no more crashes :) thx! Only when forcing anti aliasing in the ATI driver I still experience frequent crashes. (WinXP SP3, Intel C2D, 2GB, ATI HD3850 + Catalyst 8.12, no multi-client).
|
|
ISD Libertina
ISD STAR
|
Posted - 2008.12.18 12:05:00 -
[130]
Originally by: Treelox While it has improved with what 1.0.3 gave me, 1.0.4 still has a lot of mem leakage, page faults, and really starts to gobble CPU the longer I am logged in. These are not problems I had pre-1.0.3.
As a hauling/trader, I jump often, stayed logged in for hours(active), and have the market and wallet screens open constantly.
One thing I did notice, that unlike with the mem issues in 1.0.3, docked inactivity will slowly cause mem usage and cpu cycles to drop. Although still not to pre-QR levels.
Since a few people already reported experiencing page faults, here is to clear up a common misconception.
A page fault, unlike its name suggests, is not a bad thing but something created by any software to indicate to the hardware that some data it would like to work with is not currently mapped to the physical memory. While the best case scenario is having everything mapped into the physical memory at all time, it is not feasable, you are after all limited to whatever amount of RAM you have and can not load everything in there. The strategy to determine which pages (sets of data) are mapped out of memory at what time is nothing any sofware, be it eve, windows or whatever you are running simultaniously, can control but is determined by the hardware level of you computer. A page fault is the interrupt to the hardware to (re-)load a set of data, not having them would create complete chaos and shiny bluescreens of death.
For a more techy description, wikipedia is your friend.
|
|
|
Par'Gellen
Gallente The Scope
|
Posted - 2008.12.18 13:19:00 -
[131]
Edited by: Par''Gellen on 18/12/2008 13:20:36
Originally by: The Vixen I'm interested to hear what the problem was.
Hehe me too. I'm sure someone was farting around with something in the database (coincidentally on the same day as the patch) and quietly changed it back the next DT after seeing the outcry from the players. We will probably never know exactly what was going on. ---
To err is human. But it shouldn't be the company motto... |
Atharax
|
Posted - 2008.12.18 13:33:00 -
[132]
Originally by: CCP Explorer
We changed nothing in 1.0.4 on Tuesday regarding cap usage and we changed nothing today. I vote for no. 2
But as CCP Gangleri said above then we are looking into these reports.
Hello Explorer
I am as lost as anyone, yet I post this to confirm it is there.
In the past we have seen how unrelated things affect each other here in Eve. And this might be one of these.
I have a hunch though, and that from seeing the updating seem slow. Since cap is server side, and it should be to avoid exploits, it might be there where you should look.
|
|
CCP Gangleri
Minmatar
|
Posted - 2008.12.18 14:32:00 -
[133]
Originally by: Atharax
Originally by: CCP Explorer
We changed nothing in 1.0.4 on Tuesday regarding cap usage and we changed nothing today. I vote for no. 2
But as CCP Gangleri said above then we are looking into these reports.
Hello Explorer
I am as lost as anyone, yet I post this to confirm it is there.
In the past we have seen how unrelated things affect each other here in Eve. And this might be one of these.
I have a hunch though, and that from seeing the updating seem slow. Since cap is server side, and it should be to avoid exploits, it might be there where you should look.
So you are still having cap issues?
There are multiple posts above yours saying that the issue is resolved, we are still looking into this but have been unable to reproduce the effect. Please file a bug report if you have a definite reproduction case. ------------------
|
|
Nairova Intaku
|
Posted - 2008.12.18 14:36:00 -
[134]
Originally by: Par'Gellen Edited by: Par''Gellen on 18/12/2008 13:20:36
Originally by: The Vixen I'm interested to hear what the problem was.
Hehe me too. I'm sure someone was farting around with something in the database (coincidentally on the same day as the patch) and quietly changed it back the next DT after seeing the outcry from the players. We will probably never know exactly what was going on.
I fear you're right here
|
Rock'n'Roll Lady
|
Posted - 2008.12.18 14:41:00 -
[135]
what the **** is going on here, now cap issues are resolved and my characters are getting problem while getting in game and stuck on the entering game screen, happened in morning fired petition, then happening again now.
|
Atharax
|
Posted - 2008.12.18 15:17:00 -
[136]
Edited by: Atharax on 18/12/2008 15:19:38
Originally by: CCP Gangleri
So you are still having cap issues?
There are multiple posts above yours saying that the issue is resolved, we are still looking into this but have been unable to reproduce the effect. Please file a bug report if you have a definite reproduction case.
Hello Gangleri
Yes I seen the other posts, but for me the issue started today, haven't seen it previously.
Now I will backpedal somewhat though, it looks like I barked up the wrong tree.
Mostly looks it might have been some weird lag or desync issue emulating (making it look like while it isnt) the thing reported by others. After the post I did see shield continue to go down after all NPC's had been killed in one lvl 4 miss. Also cap and shield not updating after docking sitting in station a while and undocking twice. (Even unfitted the ship while inside second time.) All that point toward some kind of lag issues and not a cap bug. So yes you can safely disregard my previous post for the time being.
|
Lifelongnoob
|
Posted - 2008.12.19 12:44:00 -
[137]
i too get steadily increasing lag due to memory leak........if u plugged the memory leaks in patch 1.0.4 did u make sure the plugging material was not disolvable? cos i see a worse lag now than before patch 1.0.4... i use xp sp3 with a dual core intel cpu and 2gb or ddr 2 ram and 128mb ati graphics
|
Lorgoth
Children of Gjallarhorn
|
Posted - 2008.12.20 14:46:00 -
[138]
dropping on log in since that whole Empirean age bu11!@#$ (or whatever that crappy extension was called). still this game aint working for me.
Eve related signature below : IF... you want to be able to post on CAOD on your alt... - just join our lovely Corp (Children of Gjallarhorn) HQ at Mastakomon V - CB.
cheers
|
Ammel
|
Posted - 2008.12.21 06:09:00 -
[139]
Okay guys, Has anyone else experienced a complete system crash since the last update?
On 12/19/08 during Eve game play my computer crashed. White and black diagonal lines went across my screen and my computer shut down. It will no longer boot at all.
A few days before, my brother's computer did the same thing, with the same graphic display. Very weird since we have completely different systems. He is able to reach the bios but when it hits the Windows screen it shuts down. He lives across town in his own house. The only thing we have in common on our computers is Eve. His is a gaming computer and mine is a work computer. We have played Eve together for nearly 2 years with few problems. All this has happened since the last patch.
This might have been considered a really bad coincidence with just the two of us until this morning when another player, living across the country experienced the same thing. Again the only thing that our computers have in common is Eve.
My corp CEO had the issue with the deleted .ini file from the coding error. Is this another problem like that? If so, what do we do now?
|
|
CCP Atlas
|
Posted - 2008.12.21 10:33:00 -
[140]
Originally by: Lifelongnoob i too get steadily increasing lag due to memory leak........if u plugged the memory leaks in patch 1.0.4 did u make sure the plugging material was not disolvable? cos i see a worse lag now than before patch 1.0.4... i use xp sp3 with a dual core intel cpu and 2gb or ddr 2 ram and 128mb ati graphics
Can you open up your in-game monitor (control-shift-alt-m) when you start up the game and then when you experience these leaks take a screenshot of the 'memory graph' tab and send in in a bugreport with a description of how you arrived at the leak.
Other than that, putting resource cache to 'off' is recommended if you are experiencing memory limitations.
|
|
|
Daedalus II
|
Posted - 2008.12.21 12:29:00 -
[141]
I'm not having the cap issues, but I'm thinking this might perhaps be related to jump clones? Maybe if you make a clone jump the cap related skills are not updated properly. I base this on the fact that clone jumping is not always working properly right now as you have to log out and in again to actually see that you made a clone jump. If this doesn't work it doesn't seem far fetched to assume the skill update not to working perfectly either.
After a restart either of the game or the computer the skills might be updated correctly again and after that the people that reported problems don't have the problems anymore.
So those that reported problems: have you made a clone jump recently?
|
Astra Astus
|
Posted - 2008.12.22 18:35:00 -
[142]
I'd just like to put in my 2 cents regarding the patcher's forced-reboot that was in the notes for 1.0.3.
First off, I love the game and appreciate everything CCP does.
Anyway, I have always considered it very poor form to require a reboot after installing any piece of software. I understand the reason for this, but I'm thinking there has to be a better way.
I run Vista x64 SP1 and was told by the patcher it was going to reboot my system after applying 1.0.4. Without clicking OK, I pulled up taskmgr and found that ExeFile was still running. Is there some problem that precludes the client from properly exiting after launching the patcher? I realize you might not want the patcher to outright kill the process since somebody could be running a patched client while updating a second client, but rebooting is something I try to do infrequently.
As a workaround for those who don't like to be forced into rebooting, there is a solution. If you're not familiar with the PendingFileRenameOperations key in the registry, stop now. I'm not about to be responsible for hosing your system. I'm sure you may be used to ignoring this type of disclaimer whenever the registry is mentioned, but this is one of those keys that truly can bring the pain if you screw up.
Once the patcher has finished and is telling you it will reboot, kill the patcher process and ExeFile. Open up regedit and browse to the aforementioned value in CCS\Control\Session Manager. When viewing the RenameOps value, never hit OK since regedit has a bug that won't let you save blank lines in MULTI_SZ and will gladly strip them out for you. If there are blank lines they are needed (export the Session Manager key before opening if you are the click-happy type).
The value works in pairs of lines -- the first is the file as it exists, the second is what to rename that file. A blank line for the second line in a pair basically means delete the file in the first line. It is more complicated than that, but this should suffice for now. You should see temp files and what to rename them in your Eve folder(s). Manually perform these renames/overwrites/deletions. You can now safely delete the reg value if the only operations were for Eve and all were manually completed successfully.
Once that is done, you can run your patched Eve client without needing to reboot.
|
|
CCP Gangleri
Minmatar
|
Posted - 2008.12.23 12:02:00 -
[143]
Originally by: Astra Astus Edited by: Astra Astus on 22/12/2008 21:29:51 I'd just like to put in my 2 cents regarding the patcher's forced-reboot that was in the notes for 1.0.3.
First off, I love the game and appreciate everything CCP does.
Anyway, I have always considered it very poor form to require a reboot after installing any piece of software. I understand the reason for this, but I'm thinking there has to be a better way.
I run Vista x64 SP1 and was told by the patcher it was going to reboot my system after applying 1.0.4. Without clicking OK, I pulled up taskmgr and found that ExeFile was still running. Is there some problem that precludes the client from properly exiting after launching the patcher? I realize you might not want the patcher to outright kill the process since somebody could be running a patched client while updating a second client, but rebooting is something I try to do infrequently.
As a workaround for those who don't like to be forced into rebooting, there is a solution. If you're not familiar with the PendingFileRenameOperations key in the registry, stop now. I'm not about to be responsible for hosing your system. I'm sure you may be used to ignoring this type of disclaimer whenever the registry is mentioned, but this is one of those keys that truly can bring the pain if you screw up.
Once the patcher has finished and is telling you it will reboot, kill the patcher process and ExeFile. Open up regedit and browse to the aforementioned value in CCS\Control\Session Manager. When viewing the RenameOps value, never hit OK since regedit has a bug that won't let you save blank lines in MULTI_SZ and will gladly strip them out for you. If there are blank lines they are needed (export the Session Manager key before opening if you are the click-happy type).
The value works in pairs of lines -- the first is the file as it exists, the second is what to rename that file. A blank line for the second line in a pair basically means delete the file in the first line. It is more complicated than that, but this should suffice for now. You should see temp files and what to rename them in your Eve folder(s). Manually perform these renames/overwrites/deletions. You can now safely delete the reg value if the only operations were for Eve and all were manually completed successfully.
Once that is done, you can run your patched Eve client without needing to reboot.
Edit: I forgot to mention that an even easier workaround is to make sure ExeFile isn't running before hitting Next in the patcher.
Yes, the problem was that some users were having issues with locked files. Most likely due to the client not being closed properly for some reason. This resulted in a lot of complaints about failed patching so the patcher was changed to require a system reboot if there were locked files. This has resulted in some negative feedback but less than before. ------------------
|
|
Genji Ancient
|
Posted - 2008.12.28 16:35:00 -
[144]
Thank you for your bug report. Your report ID is 67911
I have two examples: 1 which works as described and 1 which does not work as described.
1 case a char is in the corp 7 days and corp standings update 1 case a char is in the corp 7 days and corp standings DID NOT UPDATE.
example 1 picture http://eve-files.com/dl/182507 example 2 picture http://eve-files.com/dl/182508
Can I get an answer from CCP on what is different b/c I fully expected the 2nd corp to update?
|
Estel Arador
Minmatar
|
Posted - 2008.12.28 18:06:00 -
[145]
Originally by: Genji Ancient Can I get an answer from CCP on what is different b/c I fully expected the 2nd corp to update?
It's the first one that shouldn't have been updated at that point. The second one will update at DT tomorrow.
FREE! jumpclone service |
Genji Ancient
|
Posted - 2008.12.28 18:50:00 -
[146]
Dec 21 at 01:26 until Dec 28 at 01:26 is 7 days.
Downtime is at 11:00 Eve Time on Dec 28 (today).
The character would be in corp for more than 7 days when downtime ocurred.
Every other corp has updated at 7 downtimes not 8. Therefore, the 2nd example is the error, not the first.
|
Anne Archer
|
Posted - 2009.01.05 17:39:00 -
[147]
Well, Quantum suck still sucks. I have 4 accounts and have been able to play on two systems with no problems. Eve is still crashing on exit.
Here is the system even log error: Faulting application ExeFile.exe, version 5.20.1.5197, faulting module python25.dll, version 2.5.3100.1013, fault address 0x0002bf87.
It pulled a minidump for submittal to MS that I copied out. Windows XP Professional SP (x-64) AMD 64x2 4400 (21.21GHz) 2GB of RAM ASUS A8N-SLI Premium Motherboard. Nvidia Geforce 7800 GTX
|
Adam C
Caldari H A V O C Atlas Alliance
|
Posted - 2009.01.12 20:56:00 -
[148]
severe module activation in most of the large curse battles of late gg need for speed lets add more stuff this march shall we?
|
Flexy Jerkov
|
Posted - 2009.01.13 08:40:00 -
[149]
Only issue I've been getting is the odd pc lag spikes which I assume is this memory leak issue people keep going on about. Only hangs for about 3 seconds at a time though but after a few hours it seems to happen on a more regular basis.
|
Jalava
Lutkat The Polaris Syndicate
|
Posted - 2009.01.18 18:58:00 -
[150]
After 1.0.4 something went really wrong with clone jumps:
- Pause training - Clone jump - Client hangs totally, you can see just that your pod has exited current ship -> log off & relogin - Now I'm in my new location, great
However, about 50% of time after this happens, my client is in total desync and fixed only after next DT. Following stuff has been observed:
- About 20% of random modules in all my ships in hangar are in offline state - Modules can be onlined, but they stay offline visually - Any further attempt to online module says "module is already online" - Modules seem to show themselves online and activate in space normally after another relogin. However activating module only seems to enable the effect but doesn't show module activated. For example, ships run with MWD speed but mwd is not on and no capacitor is spent and if I cloak, I cannot uncloak because cloak is not active and interference cloaking prevent me from activating cloak :)
Additional Relogins do not resolve issue and I need to wait until dt to fix state of client.
What is going on here? |
|
|
|
|
Pages: 1 2 3 4 [5] 6 :: one page |
First page | Previous page | Next page | Last page |