View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001133 | Dwarf Fortress | Init Options | public | 2010-04-14 01:25 | 2010-06-09 06:45 |
| Reporter | Thoranius | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | Dimension 4700 | OS | Windows XP | OS Version | Home Edition 5.1 |
| Product Version | 0.31.03 | ||||
| Summary | 0001133: I may have discovered the reason why the partial print option in the init tweaking fails for some people. | ||||
| Description | While using my version 0.31.02 init file as an open reference to updating my new 0.31.03 init file settings, I stumbled across this little gem. At first I thought it was perhaps due to the upgrade, but I remembered having this issue with 0.31.02 as well, until I took some instructions directly from a site. But when I messed up and left the word yes in the follow parameter [PARTIAL_PRINT:YES:0] as capitals, the flashy screen issue while fullscreened happened again. However, I noticed in the old 0.31.02 init file, that it wasn't capitalized. so I changed it to the following in 0.31.03 [PARTIAL_PRINT:yes:0] and tried again, and voila, worked like a charm. Changed it back to capitals to reproduce, and it was back to flashing. | ||||
| Steps To Reproduce | Change the init setting as follows to enable the 'blinky screen of doom' appearance. [PARTIAL_PRINT:YES:0] To make it work properly, enter it as follows. [PARTIAL_PRINT:yes:0] | ||||
| Additional Information | I assume that since all the other changeable parameters asides from numerals and filenames are capitalized, that is why this function seems not to work for a lot of players. It got me, and had I not checked my .0.31.02 init file for reference to try and troubleshoot it, I probably wouldn't of figured it out, either. | ||||
| Tags | No tags attached. | ||||
|
|
I am pretty sure not using capitols counts makes DF just run on "default" which is [PARTIAL_PRINT:NO:0]. Some have reported success by fiddling with the GFPS and the number at the end of the partial print parameter. |
|
|
Yeah, all you're doing is turning PARTIAL_PRINT off. There's a reason it's off by default -- it produces display artifacts on some machines. Does that clear things up? This should be obsolete after the merge anyway. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-04-14 01:25 | Thoranius | New Issue | |
| 2010-04-14 01:33 | PencilinHand | Note Added: 0003428 | |
| 2010-04-14 09:00 |
|
Note Added: 0003476 | |
| 2010-04-14 09:01 |
|
Tag Attached: AWAITING UPDATE | |
| 2010-04-19 19:36 |
|
Status | new => resolved |
| 2010-04-19 19:36 |
|
Resolution | open => no change required |
| 2010-04-19 19:36 |
|
Assigned To | => user6 |
| 2010-05-17 18:13 | Logical2u | Tag Detached: AWAITING UPDATE | |
| 2010-06-09 06:45 | Toady One | Status | resolved => closed |
