Damage help?

[crossram]

Well, my ignorance is seeping out again. I have two damage issues. Not happening.

I've checked, and tested...over and over, and cannot find what I'm missing. Hoping for a hint.

First thing is no prop strike. Prop diameter is set at 11.833 feet in both the airfile, and the config. Isn't the diameter what triggers a prop strike?
The part prop0_bent is made in the model, and all the rest of the prop parts work fine. I've checked naming, and such, checked prop diameter, and still no prop strike, muchless the bent prop showing.

What am I missing?

Second thing, lol!

I've got an outer wing damagebox, that won't take a hit. Part name is damagebox_r_wing2, and linked right. Both boxes on each side shows in the model viewer.

In all, so far, three damageboxes on each wing...wing1, wing2, and wing_tip. Wing1 and wing_tip take damage fine, but wing2 passes through things like it's not even there.

Again, what am I missing? Got to be something simple.

[Mathias]

Hi Ted,

propstrike, you need a contact scrape point to go along with the engine_location section, the lateral offset at least must match.

If you want to use a damagebox_r_wing2 in your model you'll also need a separate entry for it in the xdp.
If you just want a better resolution and keep it at a single wingbox entry in the xdp, call the thing damagebox_r_wing_2 (note underscore.

Edit: if you want separate wingbox entries your xdp sections and boxnames should be ordered as follows:

damagebox_r_wing
damagebox_r_wing1

[crossram]

Hello, Mathias.

Thanks! I'll recheck my scrape entries. Had already thought they were good, since a scrape point for the nose is entered, and seems to be correct. Lol. I know I've bellied in many times, trying to get the prop thing working. Even tried with a 20 foot prop...with still no strike, but the plane lays right on her belly, lol, with the prop still swinging.
Also wondered about my prop parts pivots, if that could be the hangup. :banghead:

Right, on the damagebox stuff. Originally I had 'em named wing, wing1, etc. And, of course, corrosponding in the xdp.

Systems names is a little lacking in CFS3. I'll fool with it more.

[crossram]

The added scrape point did the trick. Breaks like a charm. Just gotta make some proper splinters now. Hehe.

Now, to a freshly confusing topic. :costumes:

Let me see if I can get my story right. I had mentioned about elevator (hor. stab) trim. I haven't tried any parts naming yet, so I don't know what it might take.

You, Mathias, probably already know all this, so if you do, I'm just wondering why it won't work.

Anyway, here's what I tried. I turned AutoTrim off in the airfile (sec. 320). With the H1 loaded, I turned autotrim off. I guess CFS3 defaults it to on, when it first loads.

I had looked over the controls options, and Elevator (down and up) are assigned Num 8 and 2. Elevator Trim (down and up) are assigned Num 7 and 1.

With the H1 loaded, autotrim shut off, and 'z' on to watch elevator trim, I hit keys.

In the 'z', Num 7 and 1 set the elevator trim shown.
Num 8 and 2 did NOT affect the trim setting, but the visual elevators moved up and down.

I'm not gonna confuse things by listing my part names, except part 'Trimtab_Elevator' with keyframing hasn't worked, yet.

Elevator the key word here? And how to separate things so the right parts move.

[crossram]

Has anybody been able to make 'Lever_Elevator_Trim' work in CFS3?

So far, it seems another dud.

[Mathias]

To all I know visual trimtabs do not work in CFS3, neither in the external model nor in the VC. Wasted quite a bit of time on these to no avail.

[crossram]

Yup...irritating. I've killed a bunch of time on some of that stuff, too.

Appreciate your help, Mathias!