Madman4q2

QUOTE (Fire Blazer @ Jun 13 2014, 10:57 PM)

You can turn the camera on/off, I think this may have been mentioned at one point. I'm not sure of the hex code though, sadly (random guess is A1 00 00 00 or A2 00 00 00 but those could both be totally wrong). I'd assume it just follows whoever is currently being loaded, the camera shouldn't be causing an issue, or at least I don't recall having any problems with it. Again though, you can test it yourself. (And the EA not working can be resolved by using another computer, it's not a program that needs installing so if you have access to another computer you should be able to get it to work... unless said computer doesn't have .NET Framework............ oh, there goes that I guess, meh)

I got EA to work, but I've become so familiar with the hex that's it's pretty much a breeze coding in hex (for the most part). I know you can turn the camera auto follow off. Like I said I thought of a few ways to avoid the problem (one of them is to turn the cam off, and have the camera go to different tiles with stalls in between. The other is to simply break the reinforcements into smaller groups and load each group one after another). Like you said the camera follows whoever is being loaded - however, if a group is loaded from a single point and the individual units of that group move in opposite directions (enough so to cause a conflict) then it will happen. Like I made it happen so many times I figured out why it was being weird. I'll eventually post a video on it when I get around to fixing it, but I have a lot more important things to worry about.

QUOTE (Fire Blazer @ Jun 12 2014, 01:13 AM)

Probably has to do with the unit data, maybe where you're moving them (check the path from the loading coordinates to the starting coordinates) or the fact that you're using hex which no one uses also there's a limit of 50 units per allegiance in case you didn't know

It's not the hex bit. I think it has to do with the default cam follow thing. One thing that I know causes it is when you load multiple units from the same point and they run off in scattered directions: For example, when one unit runs all the way to the right of a large map, and another - all the way to the left of a large map. The cam doesn't know which to follow and bugs out resulting in the same effect I'm speaking of now. Often times this isn't too much of a problem since the cam only follows units still in motion. However, I'm beginning to suspect that something else might also make this happen, though I am unsure. Honestly, this isn't something I'm too woried about - but if I can avoid the situation it'd be nice.

QUOTE (Blitzzurger96 @ Jun 5 2014, 03:33 PM)

It's been so long since I've posted on this forum... whoa... Anyways, I think i have an idea about what's wrong: for your layer properties, all you had was "Main" when you also need the x length, y length and some other properties that I can't remember at all... check some random Mapping tutorial or some mapping video and it'll probably tell you the problem that I've sorta solved.

Uhhhhhhhhhhh..... do you even know what you're saying lol. I mean yes you're right- you need " ID Width Height X Y " FOR TILE CHANGE LAYERS.
You only put "Main" for the Base layer (and since this map has no tile changes there's no list like that). If you read above you would of known that it was actually the chapter name being the problem (alpha-numerical numbers only apparently). I thought it was the map because of the timing of the crash, and because I remember reading somewhere that the ship is "unusable", but I believe that was only for the town tiles (if even that). But thanks, for the post I appreciate someone trying to help !

QUOTE (Fire Blazer @ Jun 5 2014, 07:43 PM)

I'm kind of confused as to the entire point of this context But a couple of those offsets look vaguely familiar, does this perhaps involve repointing the item table? You can't just use find/replace for this thing? I'm so confused

Yes I made this for repointing the weapon table for extension purposes. I just recently tested it and noticed you need to do the same for the spell animation/association table so I'm going to post that on here too.

The copy one makes it easier to copy/paste (since you don't have to worry about "where" the table ends if you're unfamiliar with hex.
The other version is to see how Nightmare translates into hex (this is to help get a better understanding, and aid in creating additional weapons).

QUOTE (Icecube @ Jun 2 2014, 03:32 AM)

Well, add 000 for hex editor and 080 for pointer. IMO, nightmare version of them is more practical. Just a personal opinion though (since most of my modifications were transferred into nmm, and I'm having bad experience with notepad++).

Ah I see. I basically put everything straight into the hex editor with the exception of maps and tile changes (Though I have done tile changes the hard way b4). This is basically here so you can quickly copy the weapon pointer table and move it elsewhere for extension purposes (while changing the pointers so it actually works :3). As far as I know, you can't move tables and repoint to them with Nightmare (though it is helpful for finding tables and many other things). [I do use the nightmare a bit though - tis an amazing tool).