hey leute

wo geb ich den gewünschten bounce bzw. softsun wert ein den ich für meine map kompilieren will...?

gebe ich dann zb. -bounce 15 oder bounce 15, -buildcubemaps oder buildcubemaps, etc. ein...sprich mit oder ohne bindestrich

...bei Additional Game Parameters unter den feldern VIS,RAD und BSP?!

Buildcubemaps gehört ohne Bindestrich in die Console von Half-Life!
-bounce 15 gehört als Parameter hinter RAD.

Es gibt 2 Möglichkeiten, eine Kristallkugel zu benutzen:
a) um damit Spekulationen über ein Problem eines Users zu machen und
b) um sie einem besonders unkooperativen User über den Schädel zu ziehen.
- bloggt jetzt auch selbst auf Sclavia.de

wo is das RAD...

bei expert finde ich nur BSP, VIS, LIGHT, Copy File und GAME...

und wo bzw. wie in half-life?! is doch für cs:s

ingame in die console oder was?! muss ich das dann aber nur einmal machen oder?

Ja, bei Light!
CS:S hat auch ne Console!
Ja, INGAME!
JA, NUR EINMAL!

Lad dir mal Brain.exe runter und führ damit rtfm.bat aus!

Es gibt 2 Möglichkeiten, eine Kristallkugel zu benutzen:
a) um damit Spekulationen über ein Problem eines Users zu machen und
b) um sie einem besonders unkooperativen User über den Schädel zu ziehen.
- bloggt jetzt auch selbst auf Sclavia.de

ja danke aber eine letzte frage noch...

habe jetzt beim kompilieren -> expert-modus -> light.exe -> parameters: -game $gamedir $path\$file -bounce 15

nun wird kompiliert ich starte...und es sind wie komplett ohne light_environment keine schatten etc. zu sehen

was is falsch? :/

EDIT: hier der logfile:

** Executing...
** Command: "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk\bin\ep1\bin\vbsp.exe"
** Parameters: -game "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike" "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta"

Valve Software - vbsp.exe (Dec 11 2006)
4 threads
materialPath: c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike\materials
Loading c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.vmf
fixing up env_cubemap materials on brush sides...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (0)
ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (0)
Processing areas...done (0)
Building Faces...done (0)
FixTjuncs...
PruneNodes...
WriteBSP...
done (0)
writing c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.prt...done (0)
Creating default cubemaps for env_cubemap using skybox materials:
skybox/sky_day01_06*.vmt
Run buildcubemaps in the engine to get the correct cube maps.

No such variable "$hdrbasetexture" for material "skybox/sky_day01_06rt"
Can't load skybox file skybox/sky_day01_06 to build the default cubemap!
Finding displacement neighbors...
Finding lightmap sample positions...
Displacement Alpha : 0...1...2...3...4...5...6...7...8...9...10
Building Physics collision data...
done (0) (236654 bytes)
Placing detail props : 0...1...2...3...4...5...6...7...8...9...10
Compacting texture/material tables...
Reduced 952 texinfos to 481
Reduced 50 texdatas to 35 (1813 bytes to 1094)
Writing c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp
1 second elapsed

** Executing...
** Command: "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk\bin\ep1\bin\vvis.exe"
** Parameters: -game "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike" "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta"

Valve Software - vvis.exe (Nov 8 2007)
4 threads
reading c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp
reading c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.prt
620 portalclusters
1718 numportals
BasePortalVis: 0...1...2...3...4...5...6...7...8...9...10 (0)
PortalFlow: 0...1...2...3...4...5...6...7...8...9...10 (52)
Optimized: 1060 visible clusters (0.00%)
Total clusters visible: 277462
Average clusters visible: 447
Building PAS...
Average clusters audible: 614
visdatasize:99435 compressed from 99200
writing c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp
53 seconds elapsed

** Executing...
** Command: "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk\bin\ep1\bin\vrad.exe"
** Parameters: -game "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike" "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta" -bounce 15

Valve Software - vrad.exe SSE (Nov 8 2007)
----- Radiosity Simulator ----
Command line: "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk\bin\ep1\bin\vrad.exe" "-game" "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike" "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta" "-bounce" "15"

usage : vrad [options...] bspfile
example: vrad c:\hl2\hl2\maps\test

Common options:

-v (or -verbose): Turn on verbose output (also shows more command
-bounce # : Set max number of bounces (default: 100).
-fast : Quick and dirty lighting.
-final : High quality processing.
-low : Run as an idle-priority process.
-mpi : Use VMPI to distribute computations.
-rederror : Show errors in red.

-vproject <directory> : Override the VPROJECT environment variable.
-game <directory> : Same as -vproject.

Other options:
-novconfig : Don't bring up graphical UI on vproject errors.
-dump : Write debugging .txt files.
-dumpnormals : Write normals to debug files.
-threads : Control the number of threads vbsp uses (defaults to the #
or processors on your machine).
-lights <file> : Load a lights file in addition to lights.rad and the
level lights file.
-noextra : Disable supersampling.
-debugextra : Places debugging data in lightmaps to visualize
supersampling.
-smooth # : Set the threshold for smoothing groups, in degrees
(default 45).
-dlightmap : Force direct lighting into different lightmap than
radiosity.
-stoponexit : Wait for a keypress on exit.
-mpi_pw <pw> : Use a password to choose a specific set of VMPI workers.
-nodetaillight : Don't light detail props.
-centersamples : Move sample centers.
-luxeldensity # : Rescale all luxels by the specified amount (default: 1.0).
The number specified must be less than 1.0 or it will be
ignored.
-loghash : Log the sample hash table to samplehash.txt.
-onlydetail : Only light detail props and per-leaf lighting.
-maxdispsamplesize #: Set max displacement sample size (default: 512).
-softsun <n> : Treat the sun as an area light source of size <n> degrees. Produces soft shadows.
Recommended values are between 0 and 5. Default is 0.
-FullMinidumps : Write large minidumps on crash.
-chop : Smallest number of luxel widths for a bounce patch, used on edges
-maxchop : Coarsest allowed number of luxel widths for a patch, used in face interiors

-LargeDispSampleRadius: This can be used if there are splotches of bounced light
on terrain. The compile will take longer, but it will gather
light across a wider area.
-compressconstant <n> : compress lightmaps whose color variation is less than n units.
-StaticPropLighting : generate backed static prop vertex lighting
-StaticPropPolys : Perform shadow tests of static props at polygon precision
-OnlyStaticProps : Only perform direct static prop lighting (vrad debug option)
-StaticPropNormals : when lighting static props, just show their normal vector

VMPI-specific options:

[mpi]
Enable VMPI.

[-mpi_Worker]
Workers use this to connect to a VMPI job. Specify the IP address of the master. Example: -mpi_worker 1.2.3.4 or -mpi_worker 1.2.3.4:242

[-mpi_Port]
Use this on the master to force it to bind to a specified port. Otherwise it binds to 23311 (and ascending port numbers if 23311 doesn't work).

[-mpi_Graphics]
Show a graphical representation of work units [grey=work unit not sent yet, red=sent, green=completed, blue=in-process]

[-mpi_Retry]
Use this on the worker to have it retry connecting to the master forever. Otherwise it will exit if it can't connect to the master immediately.

[-mpi_AutoRestart]
Use this on the worker to have it restart with the same command line parameters after completing a job. Useful in conjunction with -mpi_Retry to have an always-on worker ready to do work.

[-mpi_TrackEvents]
Enables a debug menu during jobs (press D to access). Note: -mpi_Graphics automatically enables -mpi_TrackEvents.

[-mpi_ShowDistributeWorkStats]
After finishing a stage in the work unit processing, shows statistics.

[-mpi_TimingWait]
Causes the master to wait for a keypress to start so workers can connect before it starts. Used for performance measurements.

[-mpi_WorkerCount]
Set the maximum number of workers allowed in the job.

[-mpi_AutoLocalWorker]
Used on the master's machine. Automatically spawn a worker on the local machine. Used for testing.

[-mpi_FileTransmitRate]
VMPI file transmission rate in kB/sec.

[-mpi_Verbose]
Set to 0, 1, or 2 to control verbosity of debug output.

[-mpi_NoMasterWorkerThreads]
Don't process work units locally (in the master). Only used by the SDK work unit distributor.

** Executing...
** Command: Copy File
** Parameters: "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp" "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike\maps\cs_mvcg_beta.bsp"

** Executing...
** Command: "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\hl2.exe"
** Parameters: -dev -console -allowdebug -game "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike" +map "cs_mvcg_beta"

das Ding heißt nicht Light.exe, sondern Rad.exe

Ab mit dir zum Grundlagentutorial

Es gibt 2 Möglichkeiten, eine Kristallkugel zu benutzen:
a) um damit Spekulationen über ein Problem eines Users zu machen und
b) um sie einem besonders unkooperativen User über den Schädel zu ziehen.
- bloggt jetzt auch selbst auf Sclavia.de

da ist keine rad.exe nur light.exe

Zitat:

abe jetzt beim kompilieren -> expert-modus -> light.exe -> parameters: -game $gamedir $path\$file -bounce 15

Zitat:

usage : vrad [options...] bspfile

There is nothing wrong with high standards. It's your problem that you don't meet them.
If you think it's simple, then you have misunderstood the problem.
When a customer says "nothing has changed", assume they're lying.

heeey

danke erstmal. okay sorry aber was heißt das? bin noch nich so vertraut mit den ganzen befehlen sprich eigentlich überhaupt nicht...

wo muss das hin und wie mache ich das?!

wo ist RAD bzw. wo das hin muss???

Auf HL2 übertragen:

http://www.thewall.de/content/half-life:tutorials:expert_kompilieren?s=expert

Es gibt 2 Möglichkeiten, eine Kristallkugel zu benutzen:
a) um damit Spekulationen über ein Problem eines Users zu machen und
b) um sie einem besonders unkooperativen User über den Schädel zu ziehen.
- bloggt jetzt auch selbst auf Sclavia.de

sprich hinter das ganze muss: $path\$file.bsp ???

sprich:

parameters: -game $gamedir -bounce 150 $path\$file.bsp

?

f***. sry wegen doppelpost

Nicht immer blöde nachfragen! Selber machen!

Es gibt 2 Möglichkeiten, eine Kristallkugel zu benutzen:
a) um damit Spekulationen über ein Problem eines Users zu machen und
b) um sie einem besonders unkooperativen User über den Schädel zu ziehen.
- bloggt jetzt auch selbst auf Sclavia.de

ja ich sehe aber keinen unterschied ingame um ehrlich zu sein...nach dem probieren

also stimmts doch iwie nich...

sagt doch grade bitte wie...=(

bzw. was mach ich am besten um alles in der map heller dazustellen bzw. die schatten nicht so dunkel/extrem?

*EDIT* log analyzer zeigt keine fehler an...

** Executing...
** Command: "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk\bin\ep1\bin\vbsp.exe"
** Parameters: -game "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike" "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta"

Valve Software - vbsp.exe (Dec 11 2006)
4 threads
materialPath: c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike\materials
Loading c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.vmf
fixing up env_cubemap materials on brush sides...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (0)
ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (0)
Processing areas...done (0)
Building Faces...done (0)
FixTjuncs...
PruneNodes...
WriteBSP...
done (0)
writing c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.prt...done (0)
Creating default cubemaps for env_cubemap using skybox materials:
skybox/sky_day01_06*.vmt
Run buildcubemaps in the engine to get the correct cube maps.

No such variable "$hdrbasetexture" for material "skybox/sky_day01_06rt"
Can't load skybox file skybox/sky_day01_06 to build the default cubemap!
Finding displacement neighbors...
Finding lightmap sample positions...
Displacement Alpha : 0...1...2...3...4...5...6...7...8...9...10
Building Physics collision data...
done (0) (236654 bytes)
Placing detail props : 0...1...2...3...4...5...6...7...8...9...10
Compacting texture/material tables...
Reduced 952 texinfos to 481
Reduced 50 texdatas to 35 (1813 bytes to 1094)
Writing c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp
1 second elapsed

** Executing...
** Command: "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk\bin\ep1\bin\vvis.exe"
** Parameters: -game "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike" "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta"

Valve Software - vvis.exe (Nov 8 2007)
4 threads
reading c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp
reading c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.prt
620 portalclusters
1718 numportals
BasePortalVis: 0...1...2...3...4...5...6...7...8...9...10 (0)
PortalFlow: 0...1...2...3...4...5...6...7...8...9...10 (54)
Optimized: 1062 visible clusters (0.00%)
Total clusters visible: 277466
Average clusters visible: 447
Building PAS...
Average clusters audible: 614
visdatasize:99435 compressed from 99200
writing c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp
54 seconds elapsed

** Executing...
** Command: "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk\bin\ep1\bin\vrad.exe"
** Parameters: -game "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike" -softsun 5 "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta"

Valve Software - vrad.exe SSE (Nov 8 2007)
----- Radiosity Simulator ----
sun extent=0.087156
4 threads
[Reading texlights from 'lights.rad']
[1 texlights parsed from 'lights.rad']

Loading c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp
2754 faces
126262 square feet [18181808.00 square inches]
0 displacements
0 square feet [0.00 square inches]
2754 patches before subdivision
22556 patches after subdivision
4 direct lights
BuildFacelights: 0...1...2...3...4...5...6...7...8...9...10 (12)
BuildVisLeafs: 0...1...2...3...4...5...6...7...8...9...10 (6)
transfers 4348778, max 936
transfer lists: 33.2 megs
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (0)
Bounce #1 added RGB(63345, 60552, 59692)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (1)
Bounce #2 added RGB(21431, 20868, 20855)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (0)
Bounce #3 added RGB(7543, 7129, 6858)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (1)
Bounce #4 added RGB(2976, 2742, 2558)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (0)
Bounce #5 added RGB(1244, 1094, 959)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (1)
Bounce #6 added RGB(535, 450, 373)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (0)
Bounce #7 added RGB(238, 190, 146)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (0)
Bounce #8 added RGB(107, 81, 58)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (1)
Bounce #9 added RGB(49, 35, 23)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (0)
Bounce #10 added RGB(23, 15, 9)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (1)
Bounce #11 added RGB(10, 7, 4)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (0)
Bounce #12 added RGB(5, 3, 2)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (1)
Bounce #13 added RGB(2, 1, 1)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (0)
Bounce #14 added RGB(1, 1, 0)
GatherLight: 0...1...2...3...4...5...6...7...8...9...10 (1)
Bounce #15 added RGB(1, 0, 0)
Build Patch/Sample Hash Table(s).....Done<0.0110 sec>
FinalLightFace: 0...1...2...3...4...5...6...7...8...9...10 (0)
FinalLightFace Done
0 of 0 (0% of) surface lights went in leaf ambient cubes.
ComputePerLeafAmbientLighting: 0...1...2...3...4...5...6...7...8...9...10
Ready to Finish

Object names Objects/Maxobjs Memory / Maxmem Fullness
------------ --------------- --------------- --------
models 44/1024 2112/49152 ( 4.3%)
brushes 630/8192 7560/98304 ( 7.7%)
brushsides 3894/65536 31152/524288 ( 5.9%)
planes 1264/65536 25280/1310720 ( 1.9%)
vertexes 5231/65536 62772/786432 ( 8.0%)
nodes 1602/65536 51264/2097152 ( 2.4%)
texinfos 481/12288 34632/884736 ( 3.9%)
texdata 35/2048 1120/65536 ( 1.7%)
dispinfos 0/0 0/0 ( 0.0%)
disp_verts 0/0 0/0 ( 0.0%)
disp_tris 0/0 0/0 ( 0.0%)
disp_lmsamples 0/0 0/0 ( 0.0%)
faces 2754/65536 154224/3670016 ( 4.2%)
hdr faces 0/65536 0/3670016 ( 0.0%)
origfaces 1680/65536 94080/3670016 ( 2.6%)
leaves 1647/65536 52704/2097152 ( 2.5%)
leaffaces 3058/65536 6116/131072 ( 4.7%)
leafbrushes 1156/65536 2312/131072 ( 1.8%)
areas 2/256 16/2048 ( 0.8%)
surfedges 19893/512000 79572/2048000 ( 3.9%)
edges 11405/256000 45620/1024000 ( 4.5%)
LDR worldlights 4/8192 352/720896 ( 0.0%)
HDR worldlights 0/8192 0/720896 ( 0.0%)
waterstrips 261/32768 2610/327680 ( 0.8%)
waterverts 0/65536 0/786432 ( 0.0%)
waterindices 4845/65536 9690/131072 ( 7.4%)
cubemapsamples 21/1024 336/16384 ( 2.1%)
overlays 0/512 0/180224 ( 0.0%)
LDR lightdata [variable] 567260/0 ( 0.0%)
HDR lightdata [variable] 0/0 ( 0.0%)
visdata [variable] 99435/16777216 ( 0.6%)
entdata [variable] 15804/393216 ( 4.0%)
LDR leaf ambient 1647/65536 39528/1572864 ( 2.5%)
HDR leaf ambient 0/65536 0/1572864 ( 0.0%)
occluders 0/0 0/0 ( 0.0%)
occluder polygons 0/0 0/0 ( 0.0%)
occluder vert ind 0/0 0/0 ( 0.0%)
detail props [variable] 1/12 ( 8.3%)
static props [variable] 1/1582 ( 0.1%)
pakfile [variable] 229774/0 ( 0.0%)

Level flags = 0

Win32 Specific Data:
physics [variable] 236654/4194304 ( 5.6%)
==== Total Win32 BSP file data space used: 1851981 bytes ====

Total triangle count: 7649
Writing c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp
26 seconds elapsed

** Executing...
** Command: Copy File
** Parameters: "c:\program files (x86)\steam\steamapps\sl1tt3r\sourcesdk_content\cstrike\mapsrc\cs_mvcg_beta.bsp" "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike\maps\cs_mvcg_beta.bsp"

** Executing...
** Command: "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\hl2.exe"
** Parameters: -dev -console -allowdebug -game "c:\program files (x86)\steam\steamapps\sl1tt3r\counter-strike source\cstrike" +map "cs_mvcg_beta"

Was sind denn im Moment die Einstellungen deines Light_Environment?
Poste ALLE Keys mit Wert.

Es gibt 2 Möglichkeiten, eine Kristallkugel zu benutzen:
a) um damit Spekulationen über ein Problem eines Users zu machen und
b) um sie einem besonders unkooperativen User über den Schädel zu ziehen.
- bloggt jetzt auch selbst auf Sclavia.de

schon okay. problem gelöst

Bis zum nächsten Problem.

Es gibt 2 Möglichkeiten, eine Kristallkugel zu benutzen:
a) um damit Spekulationen über ein Problem eines Users zu machen und
b) um sie einem besonders unkooperativen User über den Schädel zu ziehen.
- bloggt jetzt auch selbst auf Sclavia.de