2f161621c3
Everything lived in one flat directory, so a diff gave no clue what area it touched and finding the file you wanted meant knowing its exact name. Twelve folders now, grouped by what a thing IS rather than what type it is - a vessel's definition, its component scenes and its upgrade resources sit together, because that is the set you read when you change one of them. buildings core controllers enemies logistics planets resources shaders surface ui vessels vfx world 332 files moved and every res:// reference rewritten - 306 files touched, including the autoload and main-scene paths in project.godot. Nothing renamed: this is purely where files sit, so the diff is a pile of pure moves and no behaviour is buried in it. ui_theme.tres, icon.svg and web_shell.html stay at the root, where Godot and the export preset expect them. Verified three ways, because a suite alone would not have caught all of it: the full 117 pass, the web export builds clean, and the game renders. The export is why that matters. The FIRST export after the move failed with "Attempt to open script 'res://GameState.gd'" - the old path - while project.godot on disk plainly said res://core/GameState.gd. That is this project's documented Android FUSE mtime trap: Godot served a cached copy of a file whose content had changed. A `touch` fixed it. Nothing in the test suite would have found that, because the suite runs from a copy on a native filesystem - the one place the bug cannot happen. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
28 lines
1.4 KiB
GDScript
28 lines
1.4 KiB
GDScript
extends ColorRect
|
|
|
|
# Feeds the starfield shader the camera's position split into a CELL INDEX
|
|
# plus a fraction within that cell, rather than a raw world position.
|
|
#
|
|
# Why: the fleet routinely reaches world coordinates in the tens of
|
|
# thousands. Handing those straight to the shader forces every downstream
|
|
# calculation (the division by cell_size, floor/fract, and especially the
|
|
# hash's internal multiplies) to work at large magnitudes, where a mobile
|
|
# GPU's float precision starts to break down - and no precision qualifier
|
|
# can fix that, since `highp` widens the type but the magnitudes stay huge.
|
|
# GDScript computes in double precision, so doing the split here and passing
|
|
# only small numbers (cell indices in the hundreds, fractions in [0,1])
|
|
# keeps the shader's arithmetic in a range it can represent exactly.
|
|
|
|
@onready var camera: Camera2D = get_node("../../Camera2D")
|
|
|
|
|
|
func _process(_delta: float) -> void:
|
|
var viewport_size: Vector2 = get_viewport_rect().size
|
|
var cell_size: float = material.get_shader_parameter("cell_size")
|
|
var p: Vector2 = camera.global_position / cell_size
|
|
var cell: Vector2 = Vector2(floor(p.x), floor(p.y))
|
|
|
|
material.set_shader_parameter("camera_cell", cell)
|
|
material.set_shader_parameter("camera_frac", p - cell)
|
|
material.set_shader_parameter("camera_zoom", 1.0 / camera.zoom.x)
|
|
material.set_shader_parameter("viewport_size", viewport_size)
|