View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005340 | The Dark Mod | Coding | public | 21.09.2020 14:25 | 02.01.2023 04:40 |
| Reporter | Geep | Assigned To | |||
| Priority | normal | Severity | normal | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | ||
| OS | Win 10 | ||||
| Product Version | TDM 2.08 | ||||
| Target Version | TDM 2.11 | Fixed in Version | TDM 2.11 | ||
| Summary | 0005340: OSPathToRelativePath mystery warning | ||||
| Description | First seen in a large map under 2.07, and continuing under 2.08: "WARNING:idFileSystem::OSPathToRelativePath failed on " That is, the warning is truncated, or reporting an empty path string. Is it possible to change the warning to provide more info about context/cause/solution? | ||||
| Steps To Reproduce | While this always recurs in my large map, whether it is reproducible elsewhere, I dunno. It was first noticed when 3 items (scaled model of a bar counter, scaled model of a 4-post awning, and a standing brazier) were added to the map. Reverting and then adding any 1 of the 3 items would trigger the warning. So it seemed not to be related to a specific texture or entity, but rather some overflow, corruption, or resource depletion. The forums indicate this truncated string was seen a few time in the distant past, and reportedly sometimes cured by avoiding "bad" textures. | ||||
| Additional Information | Here is a fragment from qconsole.log, with the 3 instances of the warning displayed: ... 0.2 seconds for BuildLightShadows WARNING:Couldn't load image: makeIntensity( textures/decals/stain01b_s) WARNING:idFileSystem::OSPathToRelativePath failed on glprogs/heatHazeWithDepth.vfp 17 GL_PROGRAM_ERROR_STRING_ARB: GL_PROGRAM_ERROR_POSITION_ARB < 0 with error Linking GLSL program heatHazeWithDepth ... glprogs/heatHazeWithDepth.vfp 18 GL_PROGRAM_ERROR_STRING_ARB: GL_PROGRAM_ERROR_POSITION_ARB < 0 with error WARNING:idFileSystem::OSPathToRelativePath failed on WARNING:idFileSystem::OSPathToRelativePath failed on ... Note regarding the above GL_PROGRAM_ERROR warnings (and others not shown) - Earlier in DMap, during "Checking optional OpenGL extensions...", all features were verified as present in my system's driver except: X - GL_EXT_depth_bounds_test not found Maybe that is causing the GL_PROGRAM_ERRORs during glprogs calls? | ||||
| Tags | No tags attached. | ||||
 |
This appears to be a shader error due to drivers. The shader structure has been completely changed since 2.08 Please re-open if this can still be replicated and attach a condump |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 21.09.2020 14:25 | Geep | New Issue | |
| 15.12.2022 18:19 | nbohr1more | Relationship added | child of 0005170 |
| 02.01.2023 04:39 | nbohr1more | Note Added: 0015668 | |
| 02.01.2023 04:40 | nbohr1more | Status | new => closed |
| 02.01.2023 04:40 | nbohr1more | Resolution | open => unable to reproduce |
| 02.01.2023 04:40 | nbohr1more | Fixed in Version | => TDM 2.11 |
| 02.01.2023 04:40 | nbohr1more | Target Version | => TDM 2.11 |
