Removing caveData (flushing the local cache) should be one of the first troubleshooting steps to take when experiencing weird behavior in CAVE. The cache lives in a folder called **caveData**, hence why this process is also referred to as removing or deleting caveData.
Then it is likely we have recently changed our production EDEX server.
There is a good chance we can recover your settings. To do so, please send a short email to [support-awips@unidata.ucar.edu](mailto:support-awips@unidata.ucar.edu) with the topic "Missing Configurations", and include the username(s) of the computer(s) you use to run CAVE.
Since the pandemic began, many users have asked if they can use X11 forwarding or ssh tunneling to remotely connect to CAVE machines. **This is not recommended or supported**, and CAVE crashes in many different ways and expresses strange behavior as well.
If that is not an option, then the only remote access we recommend is using some type of VNC.
[**RealVNC**](https://www.realvnc.com/en/) and [**nomachine**](https://www.nomachine.com) are two options that are in use with positive outcomes. [**UltraVNC**](https://www.uvnc.com) may be another option, but may have quite a delay. There *may* also be other free or paid software available that we are not aware of.
!!! warning "It is likely that any VNC option you choose will also require some software or configuration to be set on the remote machine, and this will likely require administrative privileges."
- Use our [Virtual Machine option](../install/install-cave/#method-2-linux-virtual-machine). This option allows your actual machine to stay in whichever language you choose, while allowing you to run CAVE in an environment set to English. Although we list this installation under the Windows OS, this can also be done on Linux.
This problem is most commonly seen with the direct Windows installation. It can also manifest in the Mac installation (and is possible on Linux), and the root of the problem is not having Python installed properly for CAVE to use the packages.
If the [Windows installation](install-cave.md#download-and-installation-instructions_2) was not completed properly, it is possible to see incorrect behavior when loading certain products. These are derived products which use the local machine to create and render the data. This creation is dependent upon python and its required packages working correctly.
The dataset will be available in the menus and product browser, but when loaded, no data is drawn on the editor, but an entry is added to the legend.

You may see an error that mentions the python package, **jep**.
Known datasets this can affect (this is not a comprehensive list):
- Model Winds
- Metars Winds
- METAR Station Plot
- GFS Precip Type
To correct this issue on Windows:
- Uninstall all related software (C++ Build Tools, Miniconda, Python, CAVE, pip, numpy, jep, etc)
- Redo all necessary [installation instructions in **steps 1 through 6**](install-cave.md#download-and-installation-instructions_2)
To correct this issue on Mac:
- Install the [awips-python.pkg package found on **step 1**](https://unidata.github.io/awips2/install/install-cave/#download-and-installation-instructions_3)
To correct this issue on Linux:
- When running `which python` from a terminal, make sure `/awips2/python/` is returned, if not, reset that environment variable, or re-run the [**awips_install.sh** script from our installation instructions](install-cave.md#download-and-installation-instructions)
### CAVE Map Display in Lower Left Quadrant - Windows
If you start up CAVE in Windows and notice the map is showing up only in the bottom left quadrant of your display, you will just need to tweak a few display settings.

Try following these steps to fix your issue:
- Right-click on the CAVE.exe (or shortcut) icon, select Properties
- Select the Compatibility tab
- Click "Change High DPI Settings"
- At the bottom enable "Override High DPI scaling behavior"
- Change the dropdown from Application to System
---
### Windows CAVE Start Up Error
!!! Note "This should no longer be an issue for our v20 release of AWIPS."
!!! note "These screenshots may vary from your system."
!!! warning "These instructions are <i>per connection</i>, so if you use multiple connections or switch between wired and wireless connections, you'll need to do the following for each of those connections so that CAVE will always run properly."
If you do not have an NVIDIA graphics card and driver, you may see "boxes" drawn on the editor for some of the products (**METARS Station Plots** and **Surface Winds** are the resources we're aware of), as shown below:
- Check what graphics cards are available on your machine, by going to the Apple menu (far left, upper corner) > About This Mac > Overview tab (default):
- If you see two entries at the **Graphics** line, like the image shown above, then you have two graphics cards on your system. **Intel graphics cards *may*** be able to render our products properly. In this case, you can "force" your computer to use the Intel card by running the following in a terminal:
!!! note "It may be smart to run `pmset -g` first, so you can see what the current `gpuswitch` setting is (likely `1`), that way you can revert the settings if you want them back to how they were, when not using CAVE."
Sometimes yum can get in a weird state and not know what AWIPS groups have been installed. For example if you are trying to remove AWIPS you may see an error:
```
yum groupremove "AWIPS EDEX Server"
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirror.dal.nexril.net
* elrepo: ftp.osuosl.org
* epel: mirrors.xmission.com
* extras: mirrors.cat.pdx.edu
* updates: mirror.mobap.edu
No environment named AWIPS EDEX Server exists
Maybe run: yum groups mark remove (see man yum)
No packages to remove from groups
```
To solve this issue, mark the group you want to remove and then try removing it again: