Author
|
Topic: Atlas Issues (Read 2694 times)
|
Kitsune Sniper
Guest
|
 |
« Reply #30 on: May 20, 2007, 04:53:09 pm » |
|
This topic is a great example of why I don't bother using Atlas. There's a learning curve and it's a bit cumbersome/complex to use. I guess I have a slightly different view of what a program like this should be like. No offense to Klarth of course for making a very flexible program and actually finishing and releasing it.
Dude. His program is usable by most folks. Even I could figure it out. Now, Feidian, on the other hand... |
|
|
|
|
Spikeman
Guest
|
|
« Reply #31 on: May 20, 2007, 05:03:00 pm » |
|
Now, Feidian, on the other hand...
* Shudder* Someone should really write a tutorial for Feidian. :thumbsup: |
|
|
|
|
Klarth
Guest
|
|
« Reply #32 on: May 20, 2007, 05:15:05 pm » |
|
If somebody wants to write some literature/tutorials on Atlas, they can always PM me and start working on AtlasWiki...since I have most of the basis for it complete, just need the usage examples and explanations. :p
|
|
|
|
|
Nightcrawler
Guest
|
|
« Reply #33 on: May 21, 2007, 08:30:57 am » |
|
If somebody wants to write some literature/tutorials on Atlas, they can always PM me and start working on AtlasWiki...since I have most of the basis for it complete, just need the usage examples and explanations. :p
I forgot about this. This is probably the answer. Documentation and some tutorials would probably help Atlas and it's usability immensely. In fact, it would probably even shut me up as well.  I certainly understand that with increased flexibility and control, you're generally going to have to give up a varying degree of usability and simplicity. It's a trade off. Don't me wrong. You've done a great a job and having Atlas has taken the community a step farther than it was before. I just like to talk the talk. You'll notice I can't actually deliver anything better. :laugh: I've always appreciated the code behind Atlas by the way. If I can jump into a source and understand what's going on in a few minutes time, that means something to me. I've referred people to it before for an example of a some more intelligent table handling ideas than the typical looping array scans that most of us end up doing for our first attempts at our own utilities. |
|
|
|
|
DarknessSavior
Guest
|
|
« Reply #34 on: May 21, 2007, 01:43:53 pm » |
|
Try this batch file: "atlas -d debug.txt ct.smc newgame.txt" That'll output -everything- that the program does in great detail, as well as any possible errors, to a file called debug.txt. I have this on one of my projects, for example: 12 ADDTBL Added table 'script-tbl-insert.sjs' as 'script-tbl-insert.sjs'
13 ACTIVETBL Active table is now 'Table'
14 HDR Header size is now $10
15 SMA Addressing type is now 'LINEAR'
17 JMP ROM Position is now $216D2 with max bound of $2204F
21 CREATEPTR CustomPointer 'MyPtr' Addressing 'LINEAR' Offsetting -32768 Size 16d HeaderSize $10
28 WRITE CustomPointer 'MyPtr' ScriptPos $216D2 PointerPos $2165C PointerValue $000096C2
29 WRITE CustomPointer 'MyPtr' ScriptPos $216D2 PointerPos $2165E PointerValue $000096C2
39 WRITE CustomPointer 'MyPtr' ScriptPos $216D5 PointerPos $21660 PointerValue $000096C5 [/quote Thanks for the idea, KS, but I did that already. I didn't put any pointers or anything in the first file because I just want to get ANYTHING to insert, to see if that works, and of course, it didn't. 2 ADDTBL Added table 'cte2.tbl' as 'cte2.tbl'
3 ACTIVETBL Active table is now 'Table'
4 SMA Addressing type is now 'HIROM'
5 JMP ROM Position is now $370708 Thats all I get from that. ~DS |
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #35 on: May 21, 2007, 02:36:40 pm » |
|
... uh, if you don't want to insert anything, then it's doing it's job. That's as far as it'll get if you don't add any text.
|
|
|
|
|
RedComet
Guest
|
|
« Reply #36 on: May 21, 2007, 02:42:16 pm » |
|
Found out what the problem was. Apparently Atlas read the text that was *after* the "//" and decided to choke on it. Now, why it read anything beyond the "//", I have no idea. Maybe Klarth can shed some light on the subject for us.  |
|
|
|
|
DarknessSavior
Guest
|
|
« Reply #37 on: May 21, 2007, 02:44:44 pm » |
|
... uh, if you don't want to insert anything, then it's doing it's job. That's as far as it'll get if you don't add any text.
*headdesk* :banghead: I didn't say I didn't put any TEXT in the files... I didn't add any pointer information or anything like that, like in your example. Thats all I said. I had a translated script file that Suzaku sent me, that I was trying to insert into CT, using the Atlas commands and such that I listed way at the beginning of this thread. There was PLENTY of text. And yes, care to explain why I can't comment out the original Japanese script, Klarth? I'm kinda confused on that one. ~DS |
|
|
|
|
Kajitani-Eizan
Guest
|
|
« Reply #38 on: May 21, 2007, 04:09:05 pm » |
|
that's odd. you should be able to. it werks for cless!
oh wait, that's because Cless and Klarth are buddies. too bad for you. maybe if you changed your name to Chester...
|
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #39 on: May 21, 2007, 04:29:13 pm » |
|
Comments work for me too.
|
|
|
|
|
Gideon Zhi
Guest
|
|
« Reply #40 on: May 21, 2007, 04:30:49 pm » |
|
Comments only work if they're the only thing on the line. The line *must start with* the // indicator.
|
|
|
|
|
RedComet
Guest
|
|
« Reply #41 on: May 21, 2007, 05:35:18 pm » |
|
Comments only work if they're the only thing on the line. The line *must start with* the // indicator.
Which it was: #JMP($370708)
//
// 「クロノɉۈ The first character after that first "//" is where it chokes. I opened the text up in a hex editor and instead of a normal 0x20 space after it, there was 0x8140, which I assume is SJIS or EUC (too lazy to check  ). |
|
|
|
|
Kajitani-Eizan
Guest
|
|
« Reply #42 on: May 21, 2007, 10:00:42 pm » |
|
SJIS. which is odd, because that's exactly the format i have these files from Cless in, and apparently they work fine.
|
|
|
|
|
DarknessSavior
Guest
|
|
« Reply #43 on: May 22, 2007, 01:32:53 pm » |
|
It's also odd, because the thing that we did to get Atlas to work (deleting the Japanese script from the file) worked just fine. But we tried that before, when we originally came across this issue, and it didn't work. :banghead:
~DS
|
|
|
|
|
Klarth
Guest
|
|
« Reply #44 on: May 22, 2007, 07:31:40 pm » |
|
Yeah, comments have to be the first characters of a line and must be in ASCII for it to be read.
|
|
|
|
|
|
