Lost Clipboard

[Schutt]

(2.08p2)

Today someone on help channle asked how to find the clipboard if you did set the size so small that its gone.

I imidiatly zoomed my clipboard in flight to min size and could no longer see it. I didnt find a way to get it back. Now.. the funny part was i was in a tempest and had no idea where the next airfield or enemy is cause i could no longer see my clipboard. Well next time i experiment on the ground.

Luckyly found an airfield by flying around, savely landed, went to tower. Spawned again, clipboard still gone. Relogged, clipboard still gone. No way to increase clipboard size since i no longer see it in flight. ESC key tugs it away and brings it out, i see the clipboard move, but it disappears once its fully there.

I found a solution, log out, go to game folder and edit "clipFILGHT.cfg" and "clipFLIGHTo.cfg" to set the zAxisPosition from 4.0000000 to 1.1000000. Clipboard back at full size.

But i think its a bug that i can minimize it so far that i no longer see it.

[Schatzi]

Even more funny is... Schutt came to my office and asked if there was a way to ger said "lost" keyboard back.

I was logged into TA, and having no clue myself i asked another Vet that was online (he shall remain nameless untill he chooses otherwise) if HE knew what to do. To make a long story short.... we both decreased size on our clipboards untill we "lost"them.

Only way to get them back was ALT TAB (or exit game) to desktop, edit the clip**.cfg files and/or delete all .pwl files created that day.


Now, IIRC, that "dissappearing clipboard" bug has happened in the past and had been dealt with by HT (ie made impossible).

Its hard to explain to a newbie that hardly can get his mouse set up how to get his clipboard back by editing certain files.





PS: Schutt brought up an interesting idea i havent tested yet. since clipboad size is decribes as z-position in the cfg files (ie as "distance" from observer), maybe one can get the "lost" clipboard back by increasing ground detail range....

[hitech]

Fixed for next patch