PVsyst is the bankability standard. It has been since 1992. Every financier, every lender, every independent engineer expects a PVsyst report before signing off on a utility-scale solar project. That is not changing, and PVX is not trying to change it.
But PVsyst was built for energy yield simulation, not 3D terrain design. And the gap between those two jobs is where projects lose time, accuracy, and money.
This article breaks down what each tool actually handles, where PVsyst struggles, and how PVX fills the gap without replacing anything in your bankability workflow.
What PVsyst does well
PVsyst dominates bankable energy yield simulation for good reason. Its shading engine, loss chain model, and meteo database have been validated across thousands of projects. Financiers trust it. Banks require it. Independent engineers benchmark against it.
For electrical simulation, horizon profiles, near-shading analysis, and P50/P90 energy predictions, nothing else comes close. PVsyst earned its 4.6/5 on G2 and its monopoly on the bankability report.
If your project needs a lender-ready energy yield report, you need PVsyst. Full stop.
Where PVsyst breaks down
The problems start when you try to use PVsyst for anything involving real terrain at scale.
The 3D scene builder crashes on real-world data. Models over 1GB or 500K vertices routinely crash the application. Engineers working with photogrammetry or LiDAR data must heavily decimate their terrain models before PVsyst can even open them. That decimation strips the detail that makes terrain data valuable in the first place.
Importing shading scenes from other tools triggers fatal errors. PVcase exports, for example, commonly produce an “area of 3D fields is lower than area of modules” error that blocks simulation entirely. Portrait/landscape orientation mismatches between design tools and PVsyst break bifacial simulations. These are not edge cases. They are daily frustrations for engineers working on sloped or complex sites.
PVsyst is a simulation tool, not a design tool. It does not handle layout optimization, grading analysis, cable routing, or earthwork estimation. It does not compare grading approaches. It does not calculate pile lengths against terrain. It cannot show you that 44% of your site is solid rock before the bulldozer arrives.
The interface reflects its age. Windows-only desktop application. A 4-to-6-week learning curve for new users. No collaboration features. No way to share a 3D model with a stakeholder who does not have PVsyst installed.
None of these are reasons to abandon PVsyst. They are reasons to stop asking PVsyst to do jobs it was never designed for.
What PVX handles
PVX is a terrain-aware solar design platform. It works inside AutoCAD (PVX.Cad) and in the browser (PVX.View). Its job is everything that happens before the bankability simulation: terrain analysis, layout optimization, grading comparison, cable routing, and construction documentation.
Terrain at full resolution. PVX.Cad works with your actual topographic surface inside AutoCAD. No decimation, no model simplification. Every contour, every rock classification, every slope gradient stays intact.
Grading comparison in minutes. One project compared three grading approaches (full terrain smoothing, pile-adaptive grading, and table splitting) and found a $727K difference in earthwork cost. That comparison took minutes, not days. All three approaches used the same terrain data, the same panel layout, the same site boundary.
Cable routing with real trench corridors. PVX auto-generates cable routes for multiple topologies (Line String, U String, Leapfrog) and calculates voltage drop for every individual string. On a 130 MWp project, the cabling topology choice represented a $430K cost difference.
3D visualization and stakeholder sharing. PVX.View renders the full site in 3D in the browser. No software install. Stakeholders, landowners, and project managers can review terrain, layout, and shading without touching AutoCAD or PVsyst.
What PVX does not do
PVX does not replace PVsyst for bankable yield simulation. It does not produce P50/P90 energy predictions. It does not generate the lender-required energy yield report that banks demand before financing a project.
If someone tells you they have a PVsyst alternative for bankability, be skeptical. The validation history, the financial community’s trust, and the regulatory acceptance that PVsyst has built over three decades cannot be replicated by a feature checkbox.
PVX is not trying to. Different job.
What each tool handles
| Workflow stage | PVsyst | PVX |
|---|---|---|
| Terrain analysis (slope, rock, soil) | Limited. Crashes on large models. | Full resolution terrain inside AutoCAD. Slope analysis, soil hardness mapping. |
| Layout optimization | Basic. Not its core function. | Terrain-aware layout with grading comparison. |
| Earthwork estimation | None. | Three grading approaches compared with cost estimates. |
| Cable routing and voltage drop | None. | Auto-generated routes for 3 topologies. Per-string voltage drop calculation. |
| Pile length analysis | None. | Pile coordinates against actual terrain. Flags lengths over spec. |
| Bankable energy yield simulation | Industry standard. P50/P90. Full loss chain. | Not included. Exports clean data to PVsyst. |
| Shading analysis | Gold standard for near-shading and horizon profiles. | Pre-construction shading visualization. Detailed enough for design decisions. |
| Bifacial simulation | Yes. Requires correctly oriented module data. | Exports correctly oriented data. No portrait/landscape mismatch. |
| 3D stakeholder sharing | None. Desktop only. | PVX.View: browser-based 3D viewer. No install needed. |
| Financial modeling (P50/P90, loss chain) | Yes. Banks require this output. | No. Use PVsyst. |
| Collaboration | None. Single-user desktop. | PVX.View for browser sharing. AutoCAD-native for engineering teams. |
The integrated workflow
The cleanest workflow uses both tools for what they do best.
Step 1: Terrain and design in PVX.Cad. Import your topographic survey into AutoCAD. Run slope analysis and soil classification. Optimize your layout against real terrain. Compare grading approaches. Route cables. Calculate pile lengths. Resolve every constructability issue before it becomes a change order.
Step 2: Export to PVsyst. PVX exports clean, correctly oriented module data directly to PVsyst. No manual re-entry. No orientation bugs. No scene builder crashes. The 3D shading scene imports without the vertex count problems that plague photogrammetry-based workflows.
Step 3: Bankable simulation in PVsyst. PVsyst does what it does best: energy yield prediction, loss chain analysis, financial modeling. The data it receives from PVX is already validated against real terrain, so the simulation reflects what will actually get built.
Step 4: Share with stakeholders in PVX.View. The same design lives in the browser. Project managers, landowners, and non-technical stakeholders review the 3D site without installing anything.
This is not a workaround. It is how the tools were designed to connect. PVX handles the heavy 3D terrain and design work. PVsyst handles the bankable electrical simulation. The export between them is clean because PVX was built to produce PVsyst-compatible output from day one.
Why this matters now
Solar sites are getting harder. The easy, flat land is taken. New projects sit on sloped terrain, rocky ground, and sites that punish any design tool that treats the earth as a flat plane.
PVsyst will remain the bankability standard for years to come. But the 3D scene builder was never meant to handle the terrain complexity that modern utility-scale projects demand. Forcing PVsyst to do terrain design leads to decimated models, import errors, and simulation results that do not reflect real site conditions.
PVX exists to solve that specific problem. Design on real terrain. Export clean data. Let PVsyst do the simulation it was built for.
3.8 TWp of solar projects have been designed in PVX. Every one of them included PVsyst-compatible exports. The tools work better together than either works alone.
PVX.Cad runs inside AutoCAD. PVX.View runs in the browser. Both integrate directly with PVsyst for bankable simulation workflows. See how it works on your terrain.