DescentBB

I have been looking at a free game engine (Crystal Space) that recomputes light maps in real time depending on light changes.

I might replace the D2X-XL renderer with that engine, if I find the time.

How would I make a robot face the opposite way from what it was originally facing (as in, turn it around) in DLE-XP?

EDIT: Better question: How do I rotate an object (like say, a robot) around a certain axis?

Junior Pilot wrote:How would I make a robot face the opposite way from what it was originally facing (as in, turn it around) in DLE-XP?

EDIT: Better question: How do I rotate an object (like say, a robot) around a certain axis?

Couple of things to do is.
1) Set Object Mode
2) Click on "view" and select "Editor Tool Bar".



Now right click on the object you wish to rotate.

Depending on what "face" you have selected.
You can rotate the ship however you want using the Editor Tool Bar.


Hope this helps.

Not a clue whether this is DLE or D2X, or if it's even a bug.

My camera monitor is explodey. Observe:



I'm hoping someone can tell me what's wrong.

Maybe something to do with the d2x.ini file?
What d2x.ini switches are you using?

Oh and what version of DLE-XP are you using?

Is \"my camera monitor is constantly displaying some explosion of unknown origin\" the proper translation of your post, CDS?

I think I know part of what his problem is now.

I've tested this by changing the switch -render2texture 1 to 0 in the d2x.ini file.

The 0 will make the monitor display as seen in the pic above.

All he need to do is change it to a 1 and it should fix it.

EDIT:
-render2texture 1



-render2texture 0

render2texture was set to 1 when I went into d2x.ini. I changed it to 0, and the monitor was worse. And d2x.ini I never usually touch, all the values are default.

DLE is 1.5.51, D2X is 1.8.32.

Only special eefect I'm using is the smoke.

Another problem: If I set one light of a certain type to be, say, purple, all lights of that type in that level will be purple.

Chaos Death Saurer wrote:Another problem: If I set one light of a certain type to be, say, purple, all lights of that type in that level will be purple.

X2

How do I convert an rdl to a hog?

Use yahoma and build a new hog from the rdl?

They are rdl's exported from a mission I made.

Quick question: is the source for the editor going to be released like the source for d2x-xl? Or is it already and I can't read well enough to find a link?

DLE-XP is closed source by verdict of Bryan Aamot, the author of DMB2, on which DLE-XP is based.

ok, thanks for the info

reetus wrote:How do I convert an rdl to a hog?

Use yahoma and build a new hog from the rdl?

They are rdl's exported from a mission I made.

Create a new level with DLE-XP. Save and reload that level. When reloading it, DLE-XP's hog manager is opened. Use it to delete the rdl file from the hogfile and to import your rdl file into the hog file.

Use DLE-XP's mission editor to correct mission and rdl file names that are stored in the hog file.

Is there anywhere I can get a manual or readme about the features of dle xp. I really like some or the stuff you guys do with your levels, but have no clue how to do certain things like import d3 textures, glass walls, cameras(custom robots,weapons...the list is long) and stuff like that.


and on another note...
THANK YOU WHOEVER MADE THE LIGHTING FEATURE IN DLE XP!!! You have no idea how hard it was for me to light my levels with the original d2 level editor.

Bryan Aamot made it, and I fixed and enhanced it.

You can find some DLE-XP specific stuff in my Descent 2 site's DLE-XP area, and some level editing basics here.

You can also ask questions about how to do something particular in the DLE-XP Q&A thread.

Crystal Space sucks, man. It relies on too many of its own conventions.

What do the \"strength\" and \"time\" settings in the trigger tab do?

Afaik nothing.

Probably unimplemented settings from D1.

Can you explain the Advanced Object Data editor?
----------------------------------------------------
Warning: For expert users only - use at your own risk!

mass: 262144
drag: 2162
brakes: 0
turn roll: 0
flags: 75
size: 310325
shield: 6553600

XYZ

velocity:
thrust:
rotation velocity:
rotation thrust:
model/clip: 43
frame: --
frame no.: --
----------------------------------------------------

These items were for the player ship.

How does 6553600 translate into 100 shields?

It's because there is some funny conversion (or more accurately lack thereof in this case) going on. Descent supports fractional shield values, but it internally stores them as whole numbers; to make this work, the number you generally see in the editor or in game simply takes that internal value and divides it by 65536. (This of course means that shields are counted in graduations of 1/65536.)

What you're seeing there is the raw, unconverted, number. 100 * 65536 = 6553600. I think the other numbers there - mass, drag, size etc - follow the same principle.

(In case you're interested, the reason it's 65536 is because that gives 16 bits for the \"whole\" part and 16 bits for the \"decimal\" part.)

Okay, so I'm currently making a level... And I would want a detailed explanation for each behavior in the \"Robot AI\" field, so there won't be any mistakes in robot placement and the mine itself, please.

The DMB2 manual explained what each behaviour setting did, but I don't have it on hand unfortunately, and I didn't have much like tracking down a scan/copy/etc on Google.

Here it IS

site is hard to read, some really funk fonts they used.

Thank you very much, Duper.

EDIT: It doesn't say anything about Robot AI...

What Exactly are you looking for? Alertations to bot AI via a map builder (be it DMB2 or DLE-XP) is rudimentary at best. You can alter bot AI, but it requires a bit of work using 3rd party programs. Check the D2 section on http://www.planetdescent.com for tools.

Within the mission builders, you are given a list of basic commands iirc.

Oh no, I wasn't meaning to alter the AI, I was just asking what are the differences between Still, Normal, Get Behind, etcetera. I couldn't find the info anywhere, so I just posted here.

if you list them, I'll try to give you a rundown as best as my old memeory can do.

Each bot has it's own AI behavior. These commands override that (of course).

Normal, is of course, the bot's regular AI.

Still, makes the bot stay in one spot. If you shoot at it, it will do its best to stay in that one spot while returning fire.

Get behind, I THINK causes the bot to take a defensive posture before returning aggressions if at all. They will actively dodge to the side or behind a wall if available. .. Like I said, I think.

The best way to get a feel for what each AI does, is to make a quick and dirty test level (couple of big rooms and obstacles) and throw bots with various AI in. .. make not of each bot, where they are and what AI is assigned to each of them.

It's not quick like getting an answer here, but it WILL give you a clear idea of how the bots will react and if that's what you really want or not.

Okay, then, thanks.

A question from me. How do I make monitor textures shatter when I shoot or flare them? Is there some prerequisite in the settings? I have two monitors on two oposite sides of a cube, and one will always shatter when I shoot it, the other never will. What's the big deal?