- Weather Sandbox lightning experiments begin with a suitable real-world sounding and stable simulation settings.
- Vertical resolution around 300 is recommended for more realistic results.
- Display modes help you inspect clouds, humidity, air quality, velocity, droplets, and other atmospheric behavior.
- GPU performance matters most when running larger, more detailed simulations in real time.
- Best workflow: load a sounding, configure the view, pause frequently, and compare changes systematically.
Weather Sandbox lightning Setup Basics
Weather Sandbox lightning investigations work best when you treat the simulation as a controlled atmosphere rather than a conventional action game. Start by selecting a real-world sounding, then give the model enough vertical detail to represent changing conditions. The official 2D Weather Sandbox simulation provides the core environment, presets, save-file loading, display modes, and atmospheric tools needed for this workflow.
There is no dedicated lightning-generation button or guaranteed lightning event trigger in the simulator. Instead, use the simulator to examine the atmospheric ingredients and visual changes that develop as the model runs. This approach keeps your observations tied to visible simulation behavior instead of assuming that every storm cell will produce the same result.
| Setup Area | Recommended Starting Point | Why It Matters |
|---|---|---|
| Sounding | Select a real-world sounding | Supplies the forcing used by the simulation |
| Vertical resolution | 300 | The listed guidance identifies this as a realistic setting |
| Horizontal resolution | Increase gradually | Allows stronger converging winds and longer-lasting cells |
| Performance | Dedicated GPU when available | Helps maintain real-time simulation speed |
| View mode | Fullscreen with F11 | Gives more room for reading the simulation area |
Atmospheric Setup
- Load a real-world sounding
- Begin with vertical resolution near 300
- Keep the first test focused on one variable
Visual Analysis
- Use display modes 1–9
- Inspect humidity and cloud density
- Toggle velocity vectors when studying motion
Performance Control
- Prefer a dedicated GPU
- Increase resolution in stages
- Use pause and iteration controls for careful comparisons
Begin with the default visual presentation, record what you observe, and only then switch display modes. This makes it easier to identify which atmospheric change caused a visible difference.
The simulator’s official controls and tips also recommend checking whether a laptop browser is using its dedicated GPU. If the simulation feels slow, improve browser hardware selection before immediately reducing every quality setting.
Step-by-Step Lightning Experiment Workflow
A repeatable process is more useful than chasing a single dramatic result. The following sequence is designed for comparing storm structure, cloud development, moisture distribution, and wind convergence while keeping your observations organized.
Load a Sounding
Open Weather Sandbox and select a real-world sounding from the preset menu. Treat the sounding as the initial forcing for the experiment, and avoid changing multiple setup variables before the first run.
Set Resolution
Start with vertical resolution near 300, then choose a moderate horizontal resolution. Larger horizontal resolutions can support stronger converging winds and more persistent cells, but they also demand more GPU resources.
Choose a Display
Use display modes 1–9 to inspect the atmosphere. Press C for relative humidity and cloud density, K for air quality, and Tab to show or hide velocity vectors.
Run and Pause
Press the space bar to pause or resume the model. Pause at useful stages, compare the visual state, and use PgUp or PgDn to adjust iterations per second when you need faster or slower progression.
Record the Pattern
Note the sounding, resolution, display mode, and visible storm behavior. Repeat the test with only one changed setting so that your comparison remains meaningful.
| Action | Keyboard Input | Best Use |
|---|---|---|
| Pause or resume | Space Bar | Freeze a developing atmospheric pattern |
| Show velocity vectors | Tab | Inspect wind direction and convergence |
| Show humidity and cloud density | C | Compare moisture structure and cloud coverage |
| Adjust simulation speed | PgUp / PgDn | Review changes quickly or slowly |
| Reset the view | V | Return to a clean viewing position |
| Save-file reload | L | Reload the current experiment setup |
A visible cloud or storm structure is not proof that lightning has occurred. Use the display modes and repeat runs to distinguish atmospheric development from an assumed lightning event.
When studying possible lightning-supporting conditions, focus on changes that can actually be observed: increasing cloud density, moisture contrasts, converging winds, and the persistence or weakening of cells. Keep the language of your notes precise. “Cloud density increased” is more useful than claiming that a hidden electrical event occurred without a visible indicator.
Display Modes for Storm Analysis
Weather Sandbox includes several viewing and inspection controls that are especially useful for atmospheric analysis. The most effective method is to switch between a broad visual view and a focused diagnostic view. For example, inspect the overall cell first, then use the humidity and cloud-density display to evaluate how moisture is distributed within it.
| Tool or Mode | Input | What to Examine |
|---|---|---|
| Standard display modes | 1–9 | General atmospheric structure and simulation changes |
| Air quality display | K | Air-quality patterns across the simulation |
| Humidity and cloud density | C | Moisture concentration and cloud development |
| Velocity vectors | Tab | Direction, movement, and converging flow |
| Sounding graph | G | The selected forcing profile and related information |
| Weather stations | N / M | Show stations or add and remove observation points |
| Droplets | D / X | Show droplets or follow a selected droplet |
Use the sounding graph with G when you need to reconnect the visible storm pattern to the original forcing. Weather stations can provide additional reference points: press N to show or hide them, and M to add or remove stations. These tools are useful for comparing conditions across different parts of the simulation area.
Cloud Structure
Press C to inspect relative humidity and cloud density rather than relying only on the default view.
Wind Motion
Toggle Tab to reveal velocity vectors and track movement through the simulated atmosphere.
Droplet Tracking
Use D to show droplets and X to follow a droplet when studying local movement.
Profile Context
Press G to show the sounding graph and compare the model state with its initial forcing.
Use the same display mode for the first comparison, then switch views only after recording the initial result. Consistent viewing conditions make small changes easier to identify.
For a lightning-focused experiment, the most useful combination is usually the general display, humidity and cloud density, velocity vectors, and the sounding graph. No single view explains the entire atmosphere, so rotate through these tools instead of relying on one visual layer.
Resolution and Performance Tuning
Resolution affects both the quality of the experiment and the speed at which you can observe it. The published guidance recommends vertical resolution of 300 for realistic results and notes that larger horizontal resolutions can create stronger converging winds and longer-lasting cells. Those settings should be treated as starting points rather than universal requirements.
| Goal | Setting Direction | Trade-Off |
|---|---|---|
| Realistic vertical detail | Use approximately 300 vertical resolution | Requires more processing than a very low setting |
| Stronger convergence | Increase horizontal resolution | Greater GPU demand and slower simulation on weaker hardware |
| Faster testing | Reduce resolution or iterations per second | Less detail or fewer observations per unit of time |
| Detailed review | Pause and use slower iterations | Takes longer but improves visual comparison |
| Stable real-time play | Use a dedicated GPU | Depends on browser and hardware configuration |
If performance drops, make one adjustment at a time. First verify that the browser is using the dedicated GPU on a laptop. Next, lower the horizontal resolution or reduce iterations per second. This preserves more of the experiment’s structure than changing every setting simultaneously.
The listed recommendation is a GTX 1070 or better for real-time gameplay, but actual performance can vary with browser configuration, display size, and other system activity. Treat that hardware reference as a practical guideline, not a fixed requirement.
Load the sounding first, verify GPU use, set vertical resolution near 300, and then adjust horizontal resolution until the simulation remains responsive.
Lightning Experiment Checklist:
- Select a real-world sounding before changing other variables
- Set vertical resolution near 300 for the first comparison
- Check that the browser uses the dedicated GPU when available
- Record cloud density, humidity, and velocity observations
- Repeat the test after changing only one setting
Controls Reference and Troubleshooting
The simulator includes a broad keyboard layout for navigation, tools, camera behavior, and analysis. Memorizing every command is unnecessary. Start with movement, zoom, pause, display modes, and view reset; add specialized controls as your experiments become more detailed.
| Task | Control | Practical Recommendation |
|---|---|---|
| Move the view | Arrow keys | Use for controlled panning across a storm cell |
| Zoom | Plus and minus | Zoom out for structure, zoom in for local detail |
| Drag the simulation | Middle mouse button | Reposition the simulation area manually |
| Use the selected tool | Left mouse button | Hold Ctrl or Command for the inverted action |
| Change brush size | Hold B and scroll | Adjust the tool area without opening another menu |
| Hide the interface | H | Clear the screen for visual inspection |
| Reload the save file | L | Return to the saved experiment state |
Common problems are usually configuration issues rather than failures in the atmospheric model. A view that seems empty may simply be zoomed or panned away from the active area. Slow performance may indicate integrated graphics use, excessive horizontal resolution, or an iteration rate that is too high for the current system.
| Symptom | Likely Check | Suggested Response |
|---|---|---|
| Simulation feels slow | GPU selection | Confirm the browser is using dedicated graphics |
| Storm cell is hard to see | View position or zoom | Press V, then adjust with arrows or plus/minus |
| Motion is unclear | Vector display | Press Tab to show velocity vectors |
| Cloud detail is difficult to compare | Display mode | Press C and pause the simulation |
| Experiment state changed unexpectedly | Tool action | Check the selected tool and Ctrl or Command inversion |
Before restarting, press V, pause with the space bar, and review the active display mode. Many confusing results come from view position or timing rather than the loaded atmospheric setup.
For more advanced testing, the simulator also includes a flight simulator mode with A, camera following with F, autopilot with Caps Lock, and water dropping with Z. These controls are not required for a basic lightning-focused study, but they can add a different perspective when examining the simulated environment.
Q: Does Weather Sandbox include a guaranteed lightning button?
The available control reference does not identify a dedicated lightning button or guaranteed lightning trigger. Use the simulator to study cloud density, humidity, wind convergence, and other visible atmospheric changes instead.
Q: What vertical resolution is best for Weather Sandbox lightning experiments?
Start near vertical resolution 300 because the published guidance identifies that value as producing more realistic results. Adjust it only after establishing a baseline.
Q: Which displays are most useful for storm analysis?
The general display modes, humidity and cloud density view, velocity vectors, and sounding graph provide the most useful starting set for comparing storm structure and atmospheric motion.
Q: Why is the simulation running slowly?
Performance is primarily GPU dependent. Check whether a laptop browser is using its dedicated GPU, then reduce horizontal resolution or iterations per second if necessary.