View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001270 | FSSCP | --------- | public | 2007-02-11 18:24 | 2007-02-26 19:56 |
| Reporter | thesource2 | Assigned To | phreak | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Summary | 0001270: Latest February 2007 built crashes on startup | ||||
| Description | Happens with both retail and debug, with both OpenGL and Direct3D. Debug build gives following error message: Program: D:\FS2\fs2_open_d.exe File: dtoxtm64.c Line: 67 Expression: (((long)(yr-1900)>=_BASE_YEAR)&&((long)(yr-1900)<=_MAX_YEAR64)) | ||||
| Tags | No tags attached. | ||||
|
|
check if any files in the fs2 directory have file timestams (created, modified) that occur before 1970 http://www.groupsrv.com/dotnet/post-733277.html |
|
|
It was mve files that caused this. But.... I changed modified date (which was 1831) to normal and....fs2_open displayed intro.mve with GREEN TINT!!!! (like the one in the final movie but green). I thought date changing utility was buggy, but when I just read files from CD and wrote this data to fs2 directory, problem persisted. Even more: all builts I tested (all november ones and february 2007) displayed intro.mve with green tint after that. I have no slightest idea how file date can affect the way how file is displayed, but something is really wrong. |
|
|
Sorry, I forgot that modified my links and thought that all builts have this bug. Looks like green tint bug appeared in February 2007 built |
|
|
the green tint is a different thing altogether and was fixed after that build was made. |
|
|
the green tint display problem makes it a duplicate of 0001041 |
|
|
The tint problem has nothing to do with this crash bug. If it's not an issue then fine, mark it as such (we "resolve" most everything now, not "close"), but it's not a duplicate. I'm not even sure that the green tint and red tint bugs are related yet. |
|
|
Assigning this to phreak since he was dealing with it, so that it can get a proper resolution (what ever that is). |
|
|
well the original issue isn't an FSO one anyways and has more to do with some MSCRT wierdness. Guess we know the cause in canse this happens again. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-02-11 18:24 | thesource2 | New Issue | |
| 2007-02-12 19:58 | phreak | Note Added: 0007626 | |
| 2007-02-13 00:10 | thesource2 | Note Added: 0007629 | |
| 2007-02-13 00:14 | thesource2 | Note Added: 0007630 | |
| 2007-02-13 05:51 | phreak | Note Added: 0007633 | |
| 2007-02-25 03:43 | phreak | Relationship added | duplicate of 0001041 |
| 2007-02-25 03:43 | phreak | Note Added: 0007720 | |
| 2007-02-25 03:43 | phreak | Status | new => closed |
| 2007-02-25 03:43 | phreak | Resolution | open => duplicate |
| 2007-02-25 03:52 | taylor | Note Added: 0007721 | |
| 2007-02-25 03:52 | taylor | Relationship deleted | 0001041 |
| 2007-02-25 03:53 | taylor | Assigned To | => phreak |
| 2007-02-25 03:53 | taylor | Status | closed => feedback |
| 2007-02-25 03:53 | taylor | Resolution | duplicate => reopened |
| 2007-02-25 03:53 | taylor | Note Added: 0007722 | |
| 2007-02-26 19:56 | phreak | Status | feedback => resolved |
| 2007-02-26 19:56 | phreak | Resolution | reopened => no change required |
| 2007-02-26 19:56 | phreak | Note Added: 0007732 |
