Frequently Asked Questions About Nitrode
How does Nitrode’s Visual Logic differ from traditional visual scripting?
Nitrode’s Visual Logic is tightly coupled with Godot’s scene tree and signal system—not a separate runtime. Nodes represent real engine objects (e.g., CharacterBody3D, AnimationPlayer), and connections map directly to methods, properties, and signals. This means zero translation overhead, full debugger support, and seamless round-trip editing between visual and script views.
Can I use my own art or code alongside Nitrode’s AI assets and Smart Coding?
Absolutely. Nitrode is additive—not prescriptive. Import your existing 3D models, textures, or audio. Write custom GDScript or C# classes. The AI Assistant enhances your code—it doesn’t overwrite it. Generated assets include editable source files (e.g., .png, .glb, .tres) and metadata for further refinement.
Is Nitrode cloud-based or offline-capable?
Nitrode is a native desktop application—no internet required for core functionality. AI models run locally via optimized ONNX or GGUF inference (optional GPU acceleration). Cloud connectivity is used only for optional features like community asset sharing, collaborative sessions, or model updates—ensuring privacy, performance, and reliability.
Does Nitrode support multiplayer or advanced rendering features?
Yes. Since Nitrode *is* Godot 4.0, it inherits full support for high-fidelity rendering (Vulkan, GI, SDFGI), networking (ENet, WebSocket), multiplayer (dedicated server tooling, RPCs), and XR (OpenXR). The Smart Coding Assistant helps scaffold networked object sync, latency compensation, and render pipeline extensions—documenting best practices as it generates code.
What makes Nitrode’s AI “smart” versus generic LLM coding tools?
Nitrode’s AI is trained and fine-tuned exclusively on Godot’s source, documentation, and real-world project patterns—not general programming corpora. It understands your scene hierarchy, your node relationships, and your current error context. It doesn’t guess—it reasons, validates against the engine’s type system, and proposes solutions that compile and run—first time.