Building SimsLayer

2026-02-05: I began the SimSlayer project by defining the core development stages and creating the repository structure. The core vision is to build a slicing engine capable of parsing CAD models, slicing geometry, simulating print behavior, and optimizing structures for additive manufacturing. This is not intended to be just a slicer, but a simulation-driven optimization system for 3D printing workflows.

23-01-26: I started by testing existing slicing and geometry libraries to understand baseline capabilities and limitations.

pip install PythonSLM trimesh numpy cascadio --timeout 300

At this stage, I tested pyslm (PythonSLM) for slicing logic, used trimesh for mesh handling, and generated early slicing prototypes using Copilot for experimentation and learning.

26-01-26: GUI Integration & Architecture Shift

git config --global user.name "AyFait"

git config --global user.email "sonibareayfate@gmail.com"

I realized that a purely desktop-based GUI would not support proper visualization and interaction. This led to a major architectural shift: the software must be locally web-based to enable real-time visualization, simulation, and interaction.

pip install fastapi uvicorn[standard] python-multipart pythonocc-core

Backend Reality Check — CAD Kernel Requirement

A frontend-only web system is insufficient for efficient CAD processing and geometry operations. A backend CAD kernel is mandatory for solid modeling, boolean operations, topological analysis, and slicing logic. This led to adopting pythonocc-core.

Environment Setup Issue (Critical Error)

Error: pythonocc-core does not install on native Windows CMD or standard pip environments.

conda create -n pyoccenv python=3.8

conda activate pyoccenv

conda install -c conda-forge pythonocc-core

conda activate .\.conda

pip install fastapi uvicorn[standard] python-multipart pythonocc-core

28–29-01-26: Frontend System Build (React)

npm create vite@latest my-react-app

npm install

npm start

Error: npm build failed due to dependency conflicts, version incompatibilities, and bundling failures.

30-01-26: Framework Evaluation & Migration

npx create-next-app@latest

Configuration: Tailwind CSS (Yes), TypeScript (No), ESLint (Yes), Pages Router (Yes).

Next.js runs tooling on-the-fly without polluting the system environment with global packages.

UI Enhancement Libraries

npm install framer-motion lucide-react

Current Technical State

Backend: FastAPI, pythonocc-core, Conda environment
Frontend: Next.js, Tailwind CSS, Framer Motion, Lucide React
Architecture: Local web-based system with backend CAD kernel and frontend simulation interface