saindd

If there's no 64 build configuration in the trunk yet, how do you guys do it? Ming GW?

I've just noticed that the Visual Studio 2012 project files does not contain x64 configuration. Where i can get it?

I wasn't able to find this "canFire" check. In fact, most checks are done in the onFire method call.

@triggerfish: http://wiki.torque3d.org/coder:compiling-in-linux

Thanks a lot for the hard work, guys!

My biggest problem so far is that Torque insists on using it's own libraries, instead of relying on the ones provided by Emscripten (SDL, jpeg, etc.).

How can i effectively disable the inclusion of those?

Why does it need an ASM_NASM compiler?

Following the work of CuppaDev on porting T2D to the web, i have decided to give T3D a shot. Unfortunately, it's been a dependency hell so far. Most problems arise from Windows-specific dependencies, such as DirectX and PhysX. What are the correct defines for compiling to UNIX platforms? Where i can find most compile-time library defines to disable everything, just to try the build?

Take a look at this:

https://www.garagegames.com/community/resources/view/22296

This one, @rlranft?

http://www.garagegames.com/community/forums/viewthread/127227

What about checking if the player is sprinting inside WeaponImage::onFire?

It would be nice to have that, though.

The Player class expects a model that uses the 3DS MAX Biped naming convention more or less. You can rig your player models (or other models) in any way you like, but certain bones are expected to have particular names.

Once your model is rigged just export it to COLLADA and then get it imported. Someone posted a basic walkthrough on that somewhere on the old GG forums if I recall....

So, I guess actually the answer is "NO," you cannot create new models purely in script - you have to use a modelling application to make and export them. But switching between models is done in script.

This is what i'm talking about. What are the required bone names?

Yes.

Not images, the models. They are referenced in the player datablock, OK. I can just switch that, but the code inside the player class expects some bones and tags to exist, that's what i mean by hardcoded.

Skyboxes are bad if you want more realism in the background mountain. Or a semi-far mountain:

http://i.ytimg.com/vi/sYyt-puk9a4/maxresdefault.jpg

http://i.ytimg.com/vi/d7wcGh8EmiU/maxresdefault.jpg

http://i1-games.softpedia-static.com/screenshots/-Battlefield-Bad-Company-2-Squad-Deathmatch-Gameplay-Walkthrough-Trailer_5.jpg

I'm working on some background mountains, so, what is less expensive for the T3D engine? Using low poly mesh for the background mountains, or creating a terrain from the heightmap? In Unity, for example, it's the mesh. UDK, however, is the heightmap.

Now i get it. Thanks! :)

Does T3D support terrain stitching? How many terrain objects can exist in a scene?

Randomization of rotation, size and life of the particles, so each shot can have a slightly different muzzle flash.

Is there a built-in T3D shader that allows me to blend vertex via their world position?

http://i.imgur.com/sVsRA4D.jpg

Thanks. Do you think it's reasonable to use that as a muzzle-effect base or should i create a custom class? In UE, i use particles as muzzle flashes instead of meshes inside the models. This way, the same effect applies to both FP and TP.

Can i control the spawned ParticleEmitter via script? Play, stop, change it's parameters? For example, i might want to randomize some of the properties, like velocity, etc.

Are there any examples of ParticleEmitterNode in the docs?

I have noticed that the default player model rotates the hip bone when the player aims at different locations. How is that done and how it can be implemented in custom models?

What is that property?