engine

[sniperz227]

hey i wanted to get into engine coding. i currently have downloaded all the necessary engine osurce files for kurok psp. http://www.bladebattles.com/kurok/files.html threr and the p.c one. i was wondering what the process is to get stuff in their compiled and in to the actual game(like for qc when you take the progs.dat file and put it in). I use dev c++ to compile my other c++ non quake related stuff would be able to use that for the engine?.also i was wondering if someone could link to to a tutorial on changing the background on the main menu and the color of the letters. Thanks alot

[Baker]

Compiling: viewtopic.php?t=1667

Tutorials: viewforum.php?f=12

[mh]

The first thing you should do is read this: http://www.jasonbadams.net/20081218/why ... use-dev-c/

Read it well and pay attention to it.

[qbism]

As a perpetual code noob, I'd suggest reckless' C::B Advanced package on Sourceforge. Latest mingw, libraries, and CodeBlocks in an easy install. Right click on function provides "find declaration" and "find implementation" like VC++ Express.

I also like Express 2008. I've installed Express 2010 but it's less intuitive... it removes "build" from the menu for example, (or at least I can't find it anymore), and seems like I have to right click on the solution or project name in the browser and hunt for "build".

[sniperz227]

i got vb c++ 2010 professional instead is that good?

[Baker]

On day 1, use Dev-C++ if that is what you like. Play around with engine coding and experiment. You can switch IDEs later, but to get an initial peek at what engine coding is about, it does not matter what you use on day 1.

At this point, you don't even know if you'll like doing it or if you have enough determination to get a grasp of it. You have to obtain familiarity with lot of the subsystems in the engine to make any kind of significant progress and that takes a while. And if you make a trivial mistake, the engine will crash ... versus QuakeC which will just kick out an error message.

If you find you like engine coding or want to get deeper into, you can always switch IDEs.

[That being said, the idea of learning engine coding starting with Kurok PSP is crazy. I'm sure you like the PSP, but it is a bad starting point ... even with a good setup, it takes a couple of minutes to compile and another minute or 2 to load it to the PSP and then run it (that is not a good environment for playing around ... not so bad if you can plan out your work ... but that means you already understand the engine and are not learning it), the compile process is command line interface, the Kurok PSP project itself kicks out 700 warnings (I learned a ton from those and how to solve them, but well ... that was something that interested me), the PSP can easily run out of memory, Kurok PSP is both C and C++ and a bit of assembly stuff too, the make file for the PSP is complicated. There is no way of debugging for the PSP except with "trace". A half-way decent Kurok PSP setup involves "Win32 Stubs" (files to fake a Windows development environment into thinking it can compile the PSP code without using the real headers). And Kurok PSP cannot hardly any of the engine tutorials that target other platforms. So you will be +20 on the pain level before you begin. That isn't "I'm trying to engine code the first day" territory ... that has mountains of obstacles in your path before you even get to experiment with trying the idea of doing something interesting.

To the best of my knowledge, anyone with any level of success coding on the Quake PSP platform already had a basic to strong foundation from some previous coding project. In the case of the original guys who coded the earlier forms of Quake PSP -- those guys had to have really deep coding roots.]

None of the above is meant to discourage you ... you should definitely try to compile for the PSP and try a tutorial or 2. You might really like it.

And you'll never know if you don't try.

If you do decide it is something that you want to do and feel up to, at that point follow every single word of advice from MH or that he has ever posted.

[sniperz227]

[revelator]

makefilenormal needs a suffix for the -f switch to make just rename it to makefile.normal and do make -f makefile.normal

if in doubt about ide's but you think C::B sounds interresting get the ide only package from the main C::B site. C::B can use pretty much any compiler and detects most at first start. It also works with msvc

[sniperz227]

still getting the same error?

[sniperz227]

should i use codebloacks instead of cygwin?

[Baker]

[sniperz227]

i know thats what i followed but for some reason it wont work:P i dled the enigne put the folder in home/user then cd to the enigne and then to the psp folder and typed in make -f makefilenormal

this is what my psp folder looks like :

[Baker]

(Looks like you extracted it correctly according the instructions ...)

If I remember correctly ... I am thinking that Cygwin does not play nice with UAC (Vista and Windows 7 feature)

http://www.howtogeek.com/howto/windows- ... ows-vista/

I don't recall the specifics.

Maybe this link will help ... http://frazzleddad.blogspot.com/2007/05 ... d-uac.html

But you might need to disable UAC (User Account Control) on Vista or Windows 7 otherwise Cygwin can't operate in the clear like it needs to.

I hope that solves your issue. I remember having some sort of problem when I enabled UAC on Vista with the PSP compile process not working right, but I can't recall the specifics but I knew that it had worked before and turned UAC off and then it worked again.

[sniperz227]

still not working :@

[Baker]