Pilot Archive
Thread: Anone's Chips Disappearing?
Page 1 of 1
JerethBane
Mon May 23, 2005 11:14 am
#1
Pretty steamed since this has happened to me twice now.
Couple weeks ago I got an Emergency Shield-Rear form a reb, loaded it and confirmed it. Launched and the program was missing from my FC. Other programs I got from the rebel and loaded at the same time were in my FC.
Today, got some Reactor Overload IV from a Privateer. Loaded them into my astormech and two of my flight computers, and one of the chips disappeared after loading.
Anyone else having this problem?
CNevyn
Mon May 23, 2005 11:22 am
#2
If the program on the chip is larger than your FC's free space, it tries to load it, fails, and expends the chip. known issue.
To avoid this, I load my chips first, carefully watching the numbers... then add any additional programs after.
Erahth
Mon May 23, 2005 11:37 am
#3
I've had this bug a number of times, ever since JTL was launched.
And it's not size related - at least, not for me - as I've ensured that I have adequate room in my flight computer. If I haven't had room, I've always had a dialogue box pop up and inform me that there's not enough room to install another program.
Come to think of it...it's only ever happened to me in Flight Computers that I can recall. I don't have a problem with Astromechs.
As an aside, is there any way to check how 'full' an astromech is?
CNevyn
Mon May 23, 2005 11:46 am
#4
I think you can check it's program space as well.. but, have to wait'll after the work day to look.
Otherwise, regarding the chips vanishing.. I blame Tomo. 
/throttle 1.0
/booster on
/iffscramble
*cackles*
BonesDragon
Mon May 23, 2005 1:01 pm
#5
Yeah, happened to me last week. I bought a chip, loaded it into my FC, and it was gone. I immediately went back to the same vendor, bought a second one, loaded it, and that time it worked. Very odd.
Vicotnik
Mon May 23, 2005 1:02 pm
#6
I had an issue where programs would not get uploaded when I actually uploaded them.
What seemed to cause the problem was actually a size issue, but the thing is that I found out the the "size-O-meter" (or whatchamacallit) in the droid program UI was far from precise. I had to ignore the size meter completely, and look at the datapad space on the droid to figure out the problem. This might be why it does not seem to be size related at all, while it really might be just that in the end.
psikobunny
Tue May 24, 2005 12:55 am
#8
It is a size thing in a lot of cases, its just the normal warning about a full comp isnt triggering. If you're telling us the chipped program was the first and only thing you put in and it poofed, then I'll buy its not a size thing, but I'm far more willing to believe in a broken warning than anything else at this point, based on my experiences.
Page 1 of 1