need for speed shift plugin

Come on Bro....it's not that tough. I got the motor running, Just step on the gas! As I mentioned, I have not plugged these values into Injector nor do I plan to, but there's no doubt in my mind that they'll work. If you're not familiar with the process check a previous tut I posted in the need-help-with-lock-on-and-il2 topic about two weeks ago.

...and read the tut in the X-Sim manual.
I'll be away from the RideLab until early next week. I'll check back then.
I believe in you...D :thbup:

OK I'm getting some changing values now. A while back I changed some settings on vista to allow for more RAM. In system services I turned something off that didn't allow me to get changing values in the injector. Reset it all back to factory settings and now I'm getting changing values. It was driving me crazy, :lol: wondering wtf, why can't I get any live value info. from this when you guys say you can. :lol:

I will get back too you, now testing it, i have values also in the profiler.... did you already made a profile?

Okay...i have uploaded the injector profile to the database with the name 'shift test' and i have values (6 of them, 3 from demon and 3 from cxc) in the profiler and am able to produce motion.
BUT i don't understand what is what, or how to make a decent profile.

If anyone could make a basic profile, or adjust the injector profile i uploaded, or give advice please do....

:

Regards,

Rob

I have isolated all the values separately to see whats what and i noticed there are 6 of them.
DEMON:
0x00BDDDFC
0x00BC8DC8
0x00C14AF8

CXC:
0x00BDDE08
0x00BDDE0C
0x00BDDE10

I have movement, but its way too hard, if the car just moves a little the values jump up like crazy.
When i tested the lateral values, the seat only moves forward/backward, and not sideways as it should. Am i missing a setting here?

@Demon:
Lateral G's: float: 0x00BC8DC8 * 60000, limits (-70,70)

what do you mean by 60000,limits? the min to max value? and what is -70,70?

Thanks

I am not giving up though.....

Cheers

Hey guys, looks like you're on it. Sweet!

So the mystery of val. * 60000 ,Limits -70,70 unfolds.

Step 3 in injector has 2 parts. (1) how you interpret the memory address and (2) factoring.
The 60000 thing is the factor that I use to produce a value that I can then throw a little math at to
produce a stable value. The max factor allowed by Injector is 10000. So in essence, from this step
forward, you guys are going to be working with a value that is 6 times smaller than mine.
The Limits -70,70 thing has to do with Profiler. Bring the value in as Output 1:1(G-force) and in
step 2 (set range parameters)

Maximum value (me)70 (you) 12
Minimum value (me) 1 (you) 1

Minimum value (me)-1 (you)-1
Maximum value (me)-70 (you)-12

*don't use automatic adjustment
the resolution of your axis is going to be low, only 24 steps because X-Sim only works with whole numbers at the UI level. I am away from the lab until Monday so I can't verify the Information provided above. Rock On!......D :yes:

Thanks for the reply,

In step 3 of the injector do i need to select '32 bit FLOAT'? and in step 4 the speed to G conversion?
Also in the profiler it must be something about 120000 then 12 i think, but this is not the problem i think
And i mentioned wrong lateral movement, but i think i will have to fiddle with the inverse selection in the profile on one axis.
Anyway thanks for your help
:thbup:

Look, in case NFS provided a raw value of, lets say +/- 0.01000, then you would have to mulitply the raw value with 100000 in order to get the recommended input value range of +/-1000 in the Profiler.
An incomming value of +/-1000 into the Profiler is recommended by the Injector, but +/- 10000 or 100000 are ok as well. Just +/-0...99 is not enough at all.
An input value of +/- 12 is defininitely not sufficient for the use with SCN5 actuators. As well as +/-70.

Selecting float in the injector (step 3) may do the trick to get a higher input value in the Profiler (select float, and then try to scale the value using the injector multiplier to a Profiler input value of +-1000).

Btw, the offsets you get via these adresses are g-force values already. You dont need any conversion in the Injector for these offsets at all.

To get an input value moving the Frex type simulator sideways instead of back and forward, you need to invert the input value for one axis (left SCN5) while the other axis ( right SCN5) remains uninverted.
For longitudinal forces (accelleration/braking) the axis (SCN5) have to remain either checked, or unchecked at the same time.


If the value moves the seat sideways then, but inverted, then you have to uncheck the inversion you have made on the actuator, and then check the inversion checkbox of the other actuator.

regards

When i choose FLOAT and with a x1000factor i need to use the speed -> g conversion to get high enough values....But when i choose NORMAL with a factor of x100 or so i get good high values....so what is the difference? i guess i go for NORMAL and fiddle with the factors and leave the conversion blank...

But is it wrong to do so? Maybe you can load the latest uploaded injector file 'shift test2' and have a look at it.

Many thanks for your help and tips! :clap: I learn a lot from you guys :yes:

Regards

Rob

G-conversion takes the raw value, and converts it into another format (e.g. meters/s -> meters/s²)
You'll get wrong values, though the offsets may be high enough...

If you get input values into the Profiler between +-1000 and +-100000 without conversion, you'll be fine.

Well, my answer was based on Demon' argument, that he is getting an offset of +-70 out of NFS just after multiplying the raw value with 60000.
Divide 70/60000, and you get the raw value format -> +/-0.0011...
Btw, what is a good high value? ;D

Btw, are you using CXC adresses or the ones that demon provided?

Cause the raw values they deliver may differ in format...

By high value i mean about 100000, but i am not in my sim right now, i will test further tomorrow and try to make a basic profile. I will use NORMAL and the +1000 factor and no conversion.
Thanks again for clearing things up !

I injected all 6, but i only tried demon's adresses because he explained witch one was lateral/speed/pitch.... but all six give data.

BTW this afternoon i hooked up frex simcon boxes (just a simple wire swap) and tried his software, and it worked ok, but the motion sucks, because its too hard a ride and you cannot customize anything. so i swapped back. anyway i know it will work :yes:

@ Egoexpress, thanks for stepping up to the plate. You're on the money.

@Splendiddd, I kept thinking about your ride throwing forward from a lat. val. Yes, like Egoexpress said that is a Frex thing not the value, and I'm not familiar with how you guys get that system to work. Astonishing! But if I had to guess, I'd say...check your inversion boxes.

as for the convert to G's, use that little with speed val to create longitudinal acceleration. It's also useful with Elev values to produce vertical G's.

Rock on!........................D

Could you explain this expression please? As my support is not motivated by money.

It's just an expression meaning you got it right, like you hit the nail on the head or Bingo or Bullseye and ...........

Oh, ok, it's clear now, thanks for the explanation :

Okay i have tested some modes....

When i use NORMAL the values are skyhigh, i even have to use factor 0.01 to have 'normal' motion
I looked at the nolimits rollercoaster injector file, and it also uses FLOAT, but with the new x-sim it does not work because of the 'low' factor you can choose...So with shift and choosing FLOAT the values are also too low even with x1000 factor.

Sirnoname can you please add a higher factor to the injector? (add 2 or more zeros)
Thanks in advance

And what is the exact difference to FLOAT versus NORMAL?
Is FLOAT more smooth?
I tried to make a normal profile with some lateral forces, but with NORMAL and 0,01 factor its just to shakie, i think choosing FLOAT is the solution...
Anyway i will install 2.1.0.3 and see if that works...

:uups:

Regards.

Please tell us the number of digits instead. Skyhigh is quite relative...

When you get input (disregarding if it is +-100 or +-10000), you have to calibrate it in the Profiler then. This is usually done by driving in automatic maximum adjustment-mode without crashing the vehicle, or by entering min and max manually.

If you get an input value of +-1000 into the Profiler, and you set your min/max values to 1/12 for example, your rig will freak out, as it just switches from one endposition to another.

In case of +-1000, you have to configure a max value of 1000 (or more) for example.