Magnitude Editor

#21 @Ted first off the final place you told me to stick the exec call to the magnitude editor was common.cs which is a file in the project that TGB greated so now I have to even exec a file that TGB itself creates?
Near the top in this stupidly long post is: Executing C:/Users/ohn/AppData/Roaming/GarageGames/TorqueGameBuilder/commonPrefs.cs.
Loading compiled script C:/Program Files (x86)/Torque/Torque Game Builder 1.7.5 Pro/tgb/common/gameScripts/common.cs.

Which I think is that common.cs file being called - but the magnitude editor .cs foesn;t seem to be called from it.

@eb The instructions to set it up include pasting the .cs file into a folder that didn't exist and altering lines in such .cs files as
scripts/client/default.bind.cs and scripts/client/config.cs which don't exist either - maybe they don't exist because I was supposed to create the, but that isn't stated in the manual and I am completely new at this. OK I put my hands up it also states putting the exec order in the init.cs which I never realised was something I created, but this is all because I was simply trying to set-up a project framework before I begin doing the nitty gritty. I assumed that these 2 .cs files were created automatically by TGB.

I bought TGB 2 years ago including the iPhone version when it cost $750 for both so I'm not jumping on the band wagon and getting it at a steal, I simply never got around to using it as I put a game together just using obj-C and C and never touched the game engine. I read stuff and tried examples when I first bought it but haven't touched it since.

I'm not knocking Ted or anyone, and I had forgotten what I'd read so I simply followed instructions as laid down in the magnitude editor manual and then contacted Ted when none of those files existed. I know nothing about TGB yet, I haven't cracked open the manual again because suddenly, between contacting Ted and the morning after, I find myself doing a port of the iphone game I did into Unity3D(should take 2 months) so I don't have time. But as I can spare 5 minutes to follow instructions or to make notes where someone can tell me exactly how I should put magnitude editor into the TGB project I thought I'd follow up now rather than go through this rigmarole in 2 months again.

So if you could all excuse a complete newbie and not quote 'Search is your friend' or 'RTFM' or 'Is there a problem understanding paths or the directions ?' I would appreciate some help or mot as the case may be. I mean the common.cs Ted told me to put the exec in is a file created by TGB, am I supposed to exec this as well?

Anyway, I posted the console.log because I was asked to do so, I'm sure in two months when I sit down and crack open the manual everything will become clear in which case I will either get the magnitude editor working or do myself what I wanted it for.

#22 @John: Go easy, I don't believe anything negative was meant by any comments posted. I'm redoing some directions and sending you a new .dso (see my last post) to drop in before the Magnitude Editor download itself is updated.

#23 @ Ted just seen your new post. So the common.cs being loaded in the comsolelog isn't in gameScripts though the log states: Executing C:/Users/ohn/AppData/Roaming/GarageGames/TorqueGameBuilder/commonPrefs.cs.
Loading compiled script C:/Program Files (x86)/Torque/Torque Game Builder 1.7.5 Pro/tgb/common/gameScripts/common.cs.

That is virtually at the top of the consile.log and I can follow paths and I do see 'gameScripts' in that path. But it's a bloody long console log so I can undertstand you missing the line. The thread you referred me to I did make the changes and ran it and nothing happened.

#24 @Ted I'm not getting particularly shirty for me. I put the console.log here because I was asked to. EB jumps in with a comment about following instructions and paths - well the 'paths' thing could be right but the instructions not.

I'm not that bothered I invariably sort out myself every problem I post to any forum board but hope runs eternal and because I'm distracted doing a 1000 other things I was just hoping someone might put me straight. I see no purpose in someone posting what I read as a sarcastic comment in the spirit of 'Oh no, not another f&*^&^g newbie!'.

#25 I asked a legitimate question John.
You gave no forth bearing of your skillset or detailed-attempts to make this work and I am unaware of Ted's manual since I do not license the tool. I did not know if Ted's manual spoke of T2D/TGB installation and I am unaware of how your conversation, with Ted, went because I do not have a log of it for which to read.
- I came to help.. And whether you realize it or not; people are here to help.

Unless you are overly concise with the issue from top-to-bottom, you *will* be asked questions that start from basePoint0 as to build to a conclusion properly for the situation to gain resolve.
[If Ted went on vacation and was unable to reply, then maybe my question would not have seemed so out of place?]

Now I am almost sure that you think I am being rude or some other thing right now..but nothing could be further from the truth. I am merely speaking clearly as so we do not have confusion between us.

- The last thing I would ever do is belittle a new guy.

P.S. this is a help forum, no one really 'jumps in'. :P

#26 eb@ Point taken and I apologise. I jumped down your throat partly because the way the post read was as if you were having a private conversation with Ted as if I'm not in the room, and it's a forum, we're all in the room.

I came to the forum simply because the last email I got from Ted seemed to do a Pontius Pilate(apparently not if I read a later post correctly), and I thought asking the question here might establish whether it was a T3D problem. Maybe other people had encountered it.

So again I was at fault for taking the attitude I did, so I hope you will accept an apology.

#27 NP John. Believe me, I've received worse for less, around here.

It's a very silly place sometimes. Try to avoid getting sucked into that.

#28 @eb I'll keep that in mind. I'm given to overreaction I must admit, I'll keep a lid on it in future.