Transport Tycoon Forums

Here's an OllyDB Screenshot. Hopefully this has the encessary info. This was done with no newgrf except ttdpbasew and the latest NARS.

09/07 - **EDITED SCREENSHOT**

That should be fixed in r1727.

Awesome, thanks DaleStan. It was driving me nuts

I'm having a problem with TTDP. Basically, the terminal window comes up as usual, and asks me if I'm sure I want to start TTDP. I hit y, and it begins to load. Next, the main game window comes up, but it's black. nothingness. I've left it for ten minutes, and it doesn't do a thing.

Any ideas?

If you have a custom version dxmci.dll, remove it and try then.

I do not.

WhiteHand wrote:I do not.

Ignore me then.

Hmm, I'll try starting over with my installation.

hi i use the latest nightly

my planes do not leave the hangar

why?

goalie wrote:hi i use the latest nightly

my planes do not leave the hangar

why?

Because there is a problem and you should look in the problem section where you will find that what you are looking for is already being looked at here

wallyweb wrote:

goalie wrote:hi i use the latest nightly

my planes do not leave the hangar

why?

Because there is a problem and you should look in the problem section where you will find that what you are looking for is already being looked at here

thanks wally

i was away for 5 month
and my english is not so good so i did not search

goalie wrote:thanks wally

i was away for 5 month
and my english is not so good so i did not search

Not a problem ... and welcome back.

r1829 crashes less than a minute after loading a game.

Unhandled exception: page fault on write access to 0x0059b002 in 32-bit code (0x00617338).
Register dump:
CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
EIP:00617338 ESP:0033f8f8 EBP:0043ffff EFLAGS:00010246( - 00 -RIZP1)
EAX:00000000 EBX:0000002e ECX:0000009e EDX:00000000
ESI:00000000 EDI:0059affe
Stack dump:
0x0033f8f8: 004d03ea 020f023a 0062b67f 0062b48d
0x0033f908: 0062b479 005440eb 8154ffff 02f5004f
0x0033f918: 0000023a 00563f59 004e9664 0056ed24
0x0033f928: 004e9664 000b03cd 02f50033 007b008d
0x0033f938: 020fd48d 0056eb3a 004e9664 00c00300
0x0033f948: 008d02f5 00553d5f 0056e16c 0152e5a2
Backtrace:
=>1 0x00617338 in ttdloadw.ovl (+0x217338) (0x0043ffff)
2 0x00000000 (0x00000000)
0x00617338: movb $0x0,0x4(%edi)

That crashlog is not entirely useless, but we really need the one that TTDPatch generated; it'll be called CRASH###.txt. If TTDPatch doesn't write one, see my signature.

(And can anyone make sense of that instruction? I can turn it into either movb [0], [edi+4] or movb 0, [edi+4], neither of which are even encodable.)

It looks like it's in AT&T syntax (i.e. the operands are backwards), which would make it "mov byte [edi+4], 0" in normal syntax.

DropZone wrote:It looks like it's in AT&T syntax (i.e. the operands are backwards), which would make it "mov byte [edi+4], 0" in normal syntax.

This is why I like the TTDPatch logs. They don't attempt to disassemble, so you don't have to wonder which syntax "C6 47 04 00" is using. Plus, that byte-stream dump is a lot less ambiguous than disassembly, as there are no fewer than ten other byte-sequences that would disassemble to the same instruction.

Fortunately, that instruction appears only three times, and it wasn't too hard to guess which one I broke, so you got lucky this time. r1830 should fix it. I still can't reproduce the crash; as far as my machine is concerned, I just removed a couple weird characters from the display.

hi,

as previously written in Problems with TTDPatch the newest nightly >=r1829 doesn't work anymore on my XP x64. It crashes at start after the inro (audio ist still plaiyng).
Restored nightly r1828 still works!

newgrfw.cfg has only 1 entry
TTDPBASEW.GRF

For more details look attached files.

cu
gnome

gnome wrote:For more details look attached files.

That is not "more details". "More details" is the TTDPatch-generated crashlog, or, failing that, an OllyDbg screenshot, as detailed at the other end of the link in my signature.

If it doesn't create a CRASH.TXT how can he post one?

Now some hints, cause as you can see mine crashed too:
Rename your existing configuration file and rerun. Damn, I don't have time to check which setting causes the trouble...

DaleStan wrote:

gnome wrote:For more details look attached files.

That is not "more details". "More details" is the TTDPatch-generated crashlog, or, failing that, an OllyDbg screenshot, as detailed at the other end of the link in my signature.

here you are