Description:
Update TODO.taskpaper with performance things and some other issues I've previously forgotten to note.
Commit status:
[Not Reviewed]
References:
Diff options:
Comments:
0 Commit comments
0 Inline Comments
Unresolved TODOs:
There are no unresolved TODOs
@@ -169,9 +169,23 | |||
|
169 | 169 | Sound Effects: |
|
170 | 170 | - Generic click sound (push button) |
|
171 | 171 | - Cheer/boo crowd sound effect |
|
172 |
This is a |
|
|
172 | This is a sorta easter egg and a reference to SimCity | |
|
173 | 173 | - Explosion effect (for bulldozer) |
|
174 | 174 | |
|
175 | Performance: | |
|
176 | Issues: | |
|
177 | - Seeing up to 32 ms in update on framework-release? | |
|
178 | Structural improvements: | |
|
179 | - Button to clear/thin debug buffers? | |
|
180 | Take every nth to reduce counters to past 100 measurements | |
|
181 | - Disable some timing code in release mode? | |
|
182 | Needs some way to enable it. | |
|
183 | - Avoid redrawing tiles every time? | |
|
184 | Draw tiles once | |
|
185 | Instrumentation: | |
|
186 | - Time individual sections of update loop | |
|
187 | - Time simulation | |
|
188 | - Time each engine? | |
|
175 | 189 | Other features: |
|
176 | 190 | Accessibility: |
|
177 | 191 | - Verify contrast |
@@ -239,7 +253,13 | |||
|
239 | 253 | May be due to a quirk of my Linux setup |
|
240 | 254 | - Weird ImGui crash: |
|
241 | 255 | dotnet: /home/alys/repos/outside/ImGui.NET-nativebuild/cimgui/imgui/imgui.cpp:6293: bool ImGui::Begin(const char*, bool*, ImGuiWindowFlags): Assertion `name != __null && name[0] != '\0'' failed. |
|
256 | - Crashes after exiting a game. | |
|
257 | Seems to be a draw issue (Batch hasn't begun.) | |
|
258 | In Area renderer? | |
|
259 | - | |
|
242 | 260 | Misc: |
|
261 | - Starting a game after exiting a previous one doesn't really work, afaict | |
|
262 | Also crases, but I suspect the crash isn't related. | |
|
243 | 263 | - Events may not be deleted |
|
244 | 264 | - Exits are messy (does Encompass add threading?) @done(2021-11-28) |
|
245 | 265 | Appears to be fixed by using Game.Exit |
You need to be logged in to leave comments.
Login now