Software Requirements | Petrel

for Studio users: identical to standalone, as the 3D rendering is done locally; only data updates are streamed.

For Petrel 2024 with ray traced lighting, you need an RTX-class GPU (Tensor cores). Older Quadro P-series will lack performance.

Petrel uses the GPU for:

| Component | Requirement | Recommendation | |-----------|-------------|----------------| | | SSD (SATA or NVMe) | NVMe M.2 PCIe 4.0+ | | Free space | 50 GB (software + temp) | 200+ GB (cache + project data) | | Project storage | Local or fast network | Local NVMe for active projects; NAS/cloud for archiving |

This article provides a definitive guide to Petrel’s requirements, broken down by operating system, CPU, RAM, GPU, storage, and networking. We will also cover the differences between standalone, client-server, and cloud deployments. petrel software requirements

Petrel is highly dependent on dedicated graphics for 3D rendering. Petrel 2019 Installation Guide | PDF - Scribd

: Installation requires Microsoft C++ runtimes (V9, V10, and V11). for Studio users: identical to standalone, as the

| Component | Version | Notes | |-----------|---------|-------| | | 2015–2022 (x64) | Required for plugins | | .NET Framework | 4.8 or later | Windows feature | | DirectX | 12 | For auxiliary rendering | | License manager (if floating license) | FlexNet Publisher 11.19+ | For Schlumberger license server | | Antivirus exclusions | – | Exclude Petrel folders and processes to avoid I/O bottlenecks |

| Symptom | Likely Cause | Solution | |---------|--------------|----------| | 3D rotation is choppy | GPU VRAM full or slow PCIe lane | Upgrade GPU; ensure GPU is in x16 slot | | “Out of memory” during modeling | System RAM exhausted | Increase RAM; reduce model resolution | | Long project load times | Slow SSD or fragmented project | Migrate to NVMe; clear cache | | Fault editing lags | Single-thread CPU limit | Overclock CPU or use higher IPC model | | Petrel crashes on render | DirectX driver or old GPU driver | Use NVIDIA Studio Driver (not Game Ready) | | Remote desktop is unresponsive | High network latency or jitter | Move VDI closer to user; use PCoIP instead of RDP | Petrel uses the GPU for: | Component |

This site uses cookies to remember settings, perform statistics, and improve the experience for you. By continuing the use of the site, you acknowledge our cookie policy.