PVsyst is the industry standard for bankable energy yield simulation. Every financier, every bank, every independent engineer requires a PVsyst report to validate project economics. That is not changing.
What is changing is how the 3D data gets into PVsyst.
The Problem with PVsyst’s 3D Scene Builder
PVsyst’s core strength is electrical simulation. Its 3D scene construction module is a different story.
Engineers who work with PVsyst’s near-shading module on utility-scale projects encounter a consistent set of problems:
- Memory crashes on large models. PVsyst frequently crashes when handling 3D models above 1 GB or exceeding 500,000 vertices. On utility-scale sites with detailed terrain data, this threshold is easily exceeded.
- Forced model decimation. To prevent crashes, users must heavily simplify photogrammetry models and point clouds. The decimated models lose the terrain detail that matters most for accurate shading and grading analysis.
- Import orientation bugs. When importing scenes from other CAD tools (particularly PVcase), table orientations frequently mismatch. Portrait tables appear where landscape was intended, and vice versa. In modern PVsyst versions, these orientation mismatches trigger hard errors that prevent bifacial panel simulation entirely.
- Manual rework after import. When engineers attempt to fix incorrectly oriented tables, objects “move all over the scene,” destroying the 3D layout and requiring hours of manual recalibration.
These are not edge cases. They are documented in PVsyst’s own support forums and in PVcase’s troubleshooting documentation.
Why Engineers Cannot Leave PVsyst
Despite these frustrations, PVsyst holds a position no other tool can challenge: bankability. Lenders and investors require PVsyst output as the basis for financial close. The LCOE calculations, loss diagrams, and performance ratio estimates in a PVsyst report are the industry’s common language for project valuation.
No design tool, including PVX, should claim to replace PVsyst for this purpose.
The Workflow That Eliminates the Pain
The solution is not to replace PVsyst. It is to handle the heavy 3D work in a tool built for it, and feed PVsyst clean, pre-processed data that its simulation engine can consume without crashing.
PVX.Cad handles:
- Terrain import (LiDAR, contour, survey data) at full resolution
- 3D terrain modeling without memory limits or vertex constraints
- Slope analysis across the full site envelope
- Rack placement on real terrain (not a simplified plane)
- Cable routing along actual trench corridors
- Multi-scenario grading comparison
PVsyst receives:
- Correctly oriented module layout (no portrait/landscape mismatches)
- Pre-calculated terrain surface (no decimation needed)
- String configuration and electrical parameters
- Site parameters ready for yield simulation
The handoff is a direct PVsyst-compatible export from PVX.Cad. No intermediate file conversion. No manual orientation fixes. No scene rebuilding.
What Each Tool Does Best
| Capability | PVX.Cad | PVsyst |
|---|---|---|
| Terrain import and 3D modeling | Full resolution, no vertex limits | Crashes above 500K vertices |
| Slope and soil analysis | Multi-directional slope maps, soil hardness classification | Not available |
| Grading optimization | 3 approaches compared in minutes | Not available |
| Layout on real terrain | Terrain-aware row placement | Simplified 3D scene |
| Cable routing | Real trench corridors, voltage drop per string | Not available |
| Near-shading analysis | PVX.View (raytracing on 3D terrain) | Industry standard (with 3D scene limitations) |
| Energy yield simulation | Preliminary (via PVX.View) | Bankable (required by lenders) |
| Financial modeling | PVX.View (NPV, IRR, 30-year cash flow) | Loss diagram + PR |
| Bankability reports | Not applicable | Industry standard |
The Combined Workflow
- Import terrain into PVX.Cad (full resolution, any format)
- Analyze site (slope, soil hardness, constraints)
- Design layout on real terrain (grading, racks, cables)
- Verify in 3D using PVX.View (shadow simulation, cross-sections)
- Export to PVsyst (clean, correctly oriented, no decimation)
- Run bankable simulation in PVsyst (the part it does best)
- Share with stakeholders via PVX.View (3D viewer, reports, financial model)
PVsyst focuses on what it was built for: bankable electrical simulation. PVX handles everything that happens before the simulation and everything that happens after.
PVX exports to PVsyst as a standard workflow step. No plugins required. See the integration in action at pvx.ai/contact.