0005955: Player start entity is invisible in 3.0.0pre5

ID	Project	Category	View Status	Date Submitted	Last Update

0005955	DarkRadiant	Map Editing	public	03.05.2022 16:58	05.01.2023 16:25

Reporter	Frost_Salamander	Assigned To	greebo
Priority	normal	Severity	normal	Reproducibility	always
Status	closed	Resolution	fixed
Platform	PC	OS	Windows	OS Version	10
Product Version	3.0.0
Fixed in Version	3.0.0

Summary	0005955: Player start entity is invisible in 3.0.0pre5
Description	DR version 3.0.0pre5 On this version of DR, the player start entity is invisible.
Steps To Reproduce	1. Create a new map in DR and place only the player start entity in it. Save it somewhere (let's call it test.map). 2. Close DR, then back up and delete the AppData/Roaming/DarkRadiant folder 3. start DR 3.0.0pre5 4. Open test.map. The player start entity should be visible. 5. Open either a WIP map that you are working on, or open a map from an installed FM (e.g. the training mission). The player start should be visible. 6. Close DR and Delete the AppData/Roaming/DarkRadiant folder again. 7. start DR 3.0.0pre5 8. This time, open either a WIP map that you are working on, or open a map from an installed FM. The player start should NOT be visible. Search for it using the Entity List shortcut and it should hightlight/select, but will disappear once you deselect it. 9. Now try opening test.map again. This time the player start should also NOT be visible. The behavior seems to depend on which map you open first - if it's an existing map that's part of an FM, the bug appears. If it's a clean new map that isn't part of an FM, the bug doesn't show up.
Tags	No tags attached.

Frost_Salamander 07.05.2022 11:01 reporter ~0014822 Last edited: 07.05.2022 11:09	I backed up and deleted my entire AppData/Roaming/DarkRadiant folder and restarted pre5, and the problem went away.

Frost_Salamander 07.05.2022 12:10 reporter ~0014825	Ok it doesn't seem as simple as I thought - I'm still seeing the problem. Reproducing it is difficult but I will update this issue if I make any progress. 0005956 seems related, so happy if you want to mark that as a duplicate and close and I will just update this one.

greebo 07.05.2022 12:29 administrator ~0014826	If it is related to your AppData files, can you maybe attach a zip file of that folder? Maybe I can repro it with that set of files. (We can mark the other as related. If both are symptoms of the same problem, we can always close it down as soon as we know.)

Frost_Salamander 07.05.2022 14:45 reporter ~0014827	updated steps to reproduce - I can consistently reproduce this

Frost_Salamander 07.05.2022 14:52 reporter ~0014828	adding DarkRadiant folders. One is from when the bug happens, and one is from when it is working properly DarkRadiant_with_bug.zip (12,579 bytes) DarkRadiant_without_bug.zip (12,584 bytes)

greebo 07.05.2022 16:45 administrator ~0014829	Fixed. Thanks for the hint with the training mission being loaded before this problem occurred, this was leading me to the source of the problem.

DarkRadiant: master 390fd595 07.05.2022 16:43 greebo Details Diff	0005955: Fix player start not being rendered (in a new map) after a large map has been loaded. The code to determine whether a 4-component colour is "less" than another (as used in the shader pass sorting) was prone to collisions.	Affected Issues 0005955
	mod - radiantcore/rendersystem/backend/OpenGLStateLess.h	Diff File
DarkRadiant: master 1b271917 07.05.2022 16:43 greebo Details Diff	0005955: Fix player start not being rendered (in a new map) after a large map has been loaded. The code to determine whether a 4-component colour is "less" than another (as used in the shader pass sorting) was prone to collisions.	Affected Issues 0005955
	mod - include/version.h	Diff File
	mod - radiantcore/rendersystem/backend/OpenGLStateLess.h	Diff File

Date Modified	Username	Field	Change
03.05.2022 16:58	Frost_Salamander	New Issue
06.05.2022 10:14	greebo	Status	new => acknowledged
06.05.2022 10:14	greebo	Product Version	2.14.0 => 3.0.0
07.05.2022 11:01	Frost_Salamander	Note Added: 0014822
07.05.2022 11:04	Frost_Salamander	Note Edited: 0014822
07.05.2022 11:09	Frost_Salamander	Note Edited: 0014822
07.05.2022 12:10	Frost_Salamander	Note Added: 0014825
07.05.2022 12:29	greebo	Note Added: 0014826
07.05.2022 12:29	greebo	Relationship added	related to 0005956
07.05.2022 14:45	Frost_Salamander	Steps to Reproduce Updated
07.05.2022 14:45	Frost_Salamander	Note Added: 0014827
07.05.2022 14:46	Frost_Salamander	Steps to Reproduce Updated
07.05.2022 14:47	Frost_Salamander	Steps to Reproduce Updated
07.05.2022 14:47	Frost_Salamander	Steps to Reproduce Updated
07.05.2022 14:52	Frost_Salamander	Note Added: 0014828
07.05.2022 14:52	Frost_Salamander	File Added: DarkRadiant_with_bug.zip
07.05.2022 14:52	Frost_Salamander	File Added: DarkRadiant_without_bug.zip
07.05.2022 16:12	greebo	Status	acknowledged => confirmed
07.05.2022 16:40	greebo	Relationship added	related to 0005953
07.05.2022 16:40	greebo	Assigned To	=> greebo
07.05.2022 16:40	greebo	Status	confirmed => assigned
07.05.2022 16:43	greebo	Changeset attached	=> DarkRadiant master 390fd595
07.05.2022 16:44	greebo	Changeset attached	=> DarkRadiant master 1b271917
07.05.2022 16:45	greebo	Status	assigned => resolved
07.05.2022 16:45	greebo	Resolution	open => fixed
07.05.2022 16:45	greebo	Fixed in Version	=> 3.0.0
07.05.2022 16:45	greebo	Note Added: 0014829
07.05.2022 16:46	greebo	Relationship replaced	has duplicate 0005956
05.01.2023 16:25	greebo	Status	resolved => closed

View Issue Details

Relationships

Activities

Related Changesets

Issue History

related to	0005953	closed	greebo	Wireframe object drawing order is changing between sessions
has duplicate	0005956	closed	greebo	Pointfiles no longer visible in 3.0.0pre5