AdmiralTigerclaw
Sound Developer
Expert Member
Posts: 734
Naval Commander: Forum Sound Admin
|
 |
« Reply #60 on: July 02, 2009, 11:21:16 AM » |
|
You're dumping it in 2.0 though right? It would be okay to keep in 1.3 after it's fixed, but it's just a problem weapon I've detailed elsewhere.
|
GCFA Naval Commander Veteran Player - Supreme Spaceforce Agressor Owner: Samurai Penguin Studios Listen on Last.FM |
|
|
|
NiteHawk
|
|
« Reply #61 on: July 05, 2009, 08:56:55 AM » |
|
I'm not sure, I'd probably not remove it, it could be removed in the default settings but theres no need to remove it completely, just needs to be fixed and have a proper image etc. Basicly a proper revise.
Sorry all I havent been around for a couple days, been pretty sick again.
|
|
|
|
|
NiteHawk
|
|
« Reply #62 on: July 07, 2009, 08:46:32 AM » |
|
I'm down to a few bugs left, still including the biggest, the ramcheat.
The game is pretty crash free when your 'entered' in the game, which I'm happy about. But yeah, ramcheat still exists. Has something to do with weapons (Been pinpointing the issues).
|
|
|
|
|
NiteHawk
|
|
« Reply #63 on: July 07, 2009, 10:06:41 AM » |
|
I think a reason Ramcheat might boot is because it MAY be that ramcheck checks all ships, including AI to boot. Thus if there values are wrong it may boot you. Not sure about this yet though, still in testing.
|
|
|
|
|
NiteHawk
|
|
« Reply #64 on: July 09, 2009, 08:57:56 AM » |
|
So it does seem like it's checking values of all ships, which could lead to issues because its the server managing them, not you, thus if somethings invalid on your end due to a failed packet, it could cause an issue.
Seems to mostly do with weapons. I am pretty sure most ramcheat errors that don't involve YOU are AI.
Unfortunatly so far when I do add a fix to check yourself, ramcheat spazzes out, but after the ramcheat issues at start, i haven't gotten one and has been running over night.
I need to figure out now why the initial ram cheats are giving off issues now. I have a feeling its something to do with the way AI ramcheat is handled now.
|
|
|
|
|
NiteHawk
|
|
« Reply #65 on: July 10, 2009, 04:37:20 PM » |
|
I've done a extensive amount of changes to RAM CHEAT. However, I am unsure if it is BETTER or WORSE. So far it does seem better, no more ram cheat messages so far and it only monitors your ship (I don't see why it needs to monitor AI ships online, because the server does this and could lead to issues/crashes if you get a invalid packet, which does happen sometimes, specially in lag.)
For the most part it does seem like it's happy. If anything I've hope to of decreased issues by at least 90%, maybe more.
Going to mark this as 'resolved' for now. Only a few more things to do.
|
|
|
|
|
NiteHawk
|
|
« Reply #66 on: July 10, 2009, 04:43:19 PM » |
|
Sandtrooper what mods are you using to get that interface UI bug? I cannot replicate it yet to see whats causing it.
|
|
|
|
|
Sandtrooper
|
|
« Reply #67 on: July 10, 2009, 04:49:00 PM » |
|
None. I logout and login at another server (or the same one) and boom, the UI is f'ked. I have to restart SF every bloody time if I want to switch servers.
|
 Fleet Admiral Sandtrooper 2nd in Command of TRIBE TRIBE-SD) オークエボリューション(Oak Evolution) |
|
|
|
NiteHawk
|
|
« Reply #68 on: July 11, 2009, 01:35:03 AM » |
|
Hrm alright, I'll check to make sure UI is fully flushed each time (So it always loads new)
Otherwise I'll swap back to the 1.3.4 version for loading images, which causes issues if servers use same stuff but can worry about this for 2.0 then because DX is alot nicer.
|
|
|
|
|
NiteHawk
|
|
« Reply #69 on: July 15, 2009, 05:35:48 PM » |
|
Adjustments to RAM and now you now cannot use neutral planets as shields. Not much left to do. However I cannot figure out the random rare explosion yet, it may be fixed however due to alot of pointers leaking and being solved.. We shall have to see in the future I suppose. Going to work on the UI fix now.
|
|
|
|
|
NiteHawk
|
|
« Reply #70 on: July 17, 2009, 01:52:30 AM » |
|
1.3.6 is in its final stages.
However I am unable to find the one plagging bug anymore, which involves random exploding, because its rare.
However, we will get 1.3.6 released for now so players can play who have been having issues, just in its test stages now.
|
|
|
|
|
NiteHawk
|
|
« Reply #71 on: July 20, 2009, 04:14:28 PM » |
|
1.3.6 will be released soon, most likely tommorrow or the next day.
|
|
|
|
|
