[Correct syntax for offset 3340]

Wow thank you very much Pete!!! :D

Note I inserted 25 because I see you don't switch button 12 (my 6) off until you press your own 0,0. Is that right? Is there any reason why you shouldn't switch it off when 0366 gets set?

Eventually (pretty quickly actually) the stack overflows and, bang, FS CTDs!

Now I know why my earlier versions didn't crash. They had less virtual buttons, but as soon as I added more than 6 or 7 buttons, FS started to CTD. This is also the reasons why I don't disconnect the last switch (that would be an extra button, at least the way I did it). And yes, I will use your version of course, it's indeed much cleaner, more efficient, etc., but I'm not a programmer, so I could have never come up with something like that :)

I'm at work now but as soon as I'm home I'll give it a try (I can't wait), although I'm sure it's fine now . As soon as I'm done with my "creation", I'll post the results here

Thanks again for your outstanding support Pete!!! :D

[Correct syntax for offset 3340]

Okay as far as I see the problem is in offset 3340

Yesterday evening I started with the code which I posted here during the day. It started with a CTD. When I removed line 13 FS did NOT crash.

This is the code I used:

11=W0366=0 P0,1,Cx06003340,x3FFF

12=D31E4<700000 R64,0,Cx74003478,xFFFFFE3E

13=D31E4<695000 R64,1,Cx09003340,x01

14=D31E4<500000 R64,2,C65615,0

15=D31E4<425000 R64,3,Cx09003340,x04

16=D31E4<420000 R64,4,C65706,5000

17=D31E4<415000 R64,5,Cx09003340,x10

18=D31E4<410000 R64,6,Cx74003478,x000001C2

19=D31E4<405000 R64,7,Cx09003340,x40

20=D31E4<360000 R64,8,Cx74003478,x0000028A

21=D31E4<350000 R64,9,Cx09003341,x01

22=D31E4<341000 R64,10,Cx74003478,x000002EE

23=D31E4<330000 R64,11,Cx09003341,x04

24=D31E4<310000 R64,12,Cx74003478,x000000AA

25=W0366=1 R64,13,C65706,6000

26=P0,0,Cx0A003340,x3FFF

I then deleted everything from the buttons section except for this.

[buttons]

0=P0,1,Cx05003340,x03

1=D31E4<695000 R64,1,Cx09003340,x01

FS crashed again. I don't know what's going on, but I'm starting to get really frustrated.

I even thought for a brief moment that it's because the trouble is in line #13or because my last button is button #13 ...

No seriously, I tried everything. I changed the altitude (695000), I changed the button numbers, I changed the "Cx05003340" part to "Cx06003340" and "Cx07003340", then the "Cx09003340" part to "Cx0A003340" and "Cx0B003340" but it makes no difference. As soon as this line is reached it's a CTD :?

Regards, Chris

[Correct syntax for offset 3340]

Hi Pete,

Thanks for the quick reply. I'll try to explain my "code" line by line :-)

1. By "automatic trim" (sorry, poor choice of words) I mean this: a side effect of adding ambient wind is that the nose

of the aircraft goes down a bit while the wind is applied. Also, to keep the nose up in the flare you need to apply

constant pressure on the joystick. Maybe in RL it's the same I don't know... So by trimming the nose up, it's

easier to keep it there. It's difficult to explain but it works well.

2. Joystick 0, button 1 is my autopilot disconnect switch. I "switch on" the ground effect when I disconnect the

autopilot. I also wanted to create a different ground effect for takeoff (with reverse sign for the condition

i.e. D31E4>350000 more ambient wind, D31E4>400000 less ambient wind, etc).

So you really mean the sim (i.e. FS itself) crashes, or just the aircraft?

Yes FS itself crashes, i.e. CTD, with no windows messages

Or of course x01, x02, x04, x08, x10, x20, x40, x80 if you use hex

Do you mean that I could use decimal?. Hmm I find it easier if it's decimal.

it would be easier to see what was going on here if you used the radio altitude in metres at W31E6

Thanks for the tip, I'll give it a try.

Now for the code (I've reworked the "Offset Byte/Word ClrBits/Setbits" part, I hope it's OK now.):

12=W0366=0 P0,1,Cx06003344,x3FFF ;"switches on the ground effect" it works in the air only, otherwise FS crashes

13=D31E4<700000 R64,0,Cx74003478,xFFFFFE3E ;negative Y wind - the aircraft doesn't "baloon" when you pull up the nose - looks closer to reality

14=D31E4<680000 R64,1,Cx09003340,x01 ;switches off the above button

15=D31E4<500000 R64,2,C65615,0 ;this is the automatic trim i was talking about - it's starts trimming and is turned off at the next line

16=D31E4<425000 R64,3,Cx09003340,x04 ;switches off the above button

17=D31E4<420000 R64,4,C65706,5000 ;sets the trim - there's no way to tell "C65615" when to stop trimming and so I have to stop it at some point and then set it to a certain value

18=D31E4<415000 R64,5,Cx09003340,x10 ;switches off the above button

19=D31E4<410000 R64,6,Cx74003478,x000001C2 ;ground effect ~ 10ft

20=D31E4<405000 R64,7,Cx09003340,x40 ;switches off the above button

21=D31E4<360000 R64,8,Cx74003478,x0000028A ;ground effect ~ 5ft

22=D31E4<350000 R64,9,Cx09003345,x01 ;switches off the above button

23=D31E4<341000 R64,10,Cx74003478,x000002EE ;ground effect ~ 2ft

24=D31E4<330000 R64,11,Cx09003345,x04 ;switches off the above button

25=D31E4<310000 R64,12,Cx74003478,x000000AA ;removes most of the ground effect very close to the rwy - this way the a/c "steps" firmly on the runway on touch down. there's no way to explain this, but it works as I want it

26=W0366=1 R64,13,C65706,6000 ;add more trim on touchdown otherwise the nose slams on the runway as if all passengers are in the cockpit

27=P0,0,Cx0A003340,x3FFF ;when I press the brakes I switch off all virtual buttons

Second, it looks most intreresting and I expect I could spend a few pleasant hours working out

exactly what you are doing

Thank you :-D I'm happy I've created something interesting (if I can get it to work properly of course). I used to have some working versions, but as I added new lines it all stopped working. A few other conclusions I made:

I've watched several videos over and over again, to see what happens IRL and then I test it in the sim. I keep changing the data until I'm satisfied. The results are very good IMO. The "downside" is that this "ground effect" cannot be used for every a/c because radio altitude is measured from the datum point of the a/c which is different for every a/c (Did I miss an offset for that, i.e. something that calculates the altitude from the wheels to the ground?). Pitch is also important because the datum point is not always exactly above the wheels.

I hope this is more understandable now. Explaining isn't my best skill :-)

Regards, Chris

[Correct syntax for offset 3340]

Hello everyone,

I started experimenting with ambient wind at offset 3478 to simulate ground effect. It worked to some extent and when I started experimenting with "automatic" trim up during the flare the problems started.

As far as I can see, line 13 works fine and then the sim crashes at around 20 feet AGL (somewhere around lines 16-20). I think the problem is with my parameters/syntax for offset 3340. I also tried with offset byte setbits/clrbits, but it makes no difference.

This is the piece that's causing the trouble:

11=W0366=0 P0,1,Cx07003340,x000000FF ;joy 64 btns 1-8

12=W0366=0 P0,1,Cx07003344,x0000003F ;joy 65 btns 1-5

13=D31E4<700000 R64,0,Cx74003478,xFFFFFE3E

14=D31E4<680000 R64,1,Cx0B003340,x00000001

15=D31E4<500000 R64,2,C65615,0

16=D31E4<425000 R64,3,Cx0B003340,x00000004

17=D31E4<420000 R64,4,C65706,5000

18=D31E4<415000 R64,5,Cx0B003340,x00000010

19=D31E4<410000 R64,6,Cx74003478,x000001C2

20=D31E4<405000 R64,7,Cx0B003340,x00000040

21=D31E4<360000 R65,0,Cx74003478,x0000028A

22=D31E4<350000 R65,1,Cx0B003344,x00000001

23=D31E4<341000 R65,2,Cx74003478,x000002EE ;ground effect 2ft

24=D31E4<330000 R65,3,Cx0B003344,x00000004

25=D31E4<310000 R65,4,Cx74003478,x000000AA

26=W0366=1 R65,5,C65706,6000

27=P0,0,Cx0B003340,x000000FF

28=P0,0,Cx0B003344,x0000003F

I've been reading the forums, the SDK, etc, etc for over a month, reworked/corrected the ini 1000 times, but now I'm completely lost... Please help, what am I doing wrong?

[Fiddling with buttons & Offset conditions]

Hi Pete,

Thanks for the reply.

It sounds like what you really want is a latching switch, not a button. Is that right? If so, use your button to toggle a bit in the Virtual Button offsets (3340), and program that virtual button to (conditionally) send the control for offset 3478 repetitively.

Aaaah, so that's what I've missed in the docs. Yes that's right - I need a latching switch. I want to switch it on before landing (a/p disconnect button?) and wait for the "ground effect" at 8-10 feet radio altitude.

Another thing is that there is less drag when the a/c is in ground effect, unfortunately that's impossible to simulate in FSunless I've missed something again.

Less drag / more lift that's why you need to cut the throttle - in FS the effect is that the a/c drops like a stone on the runwayHmmm, I can try Throttle_10 just to see the effect ...

And then why you have the button send a key which sends a control. Why not have the control programmed on the button instead of the keypress?

That was only for testing pusposes - by pressing a key I can see the effect on the aircraft right away, otherwise I'll have to wait until my condition is met.

I'll play with this and report back! FSUIPC is really amazing!!

Many thanks! :D

[Fiddling with buttons & Offset conditions]

Dear Pete, hi everyone

A few days ago I had this idea to simulate something like "ground effect" by using ambient wind at offset 3478. I then assigned a key via the keys page in FSUIPC and then added an offset condition in the ini file (i.e. only add ground effect a few feet above the runway). Something like this:

[buttons]

0=D31E4<400000 R0,27,K85,8

[Keys]

0=85,8,x7C003478,x00000352

It worked like a charm, but I decided to use a flag and a virtual button, like this:

[buttons]

0=P0,1,C1003,2565

1=D31E4<400000 H10,5,K85,8

[Keys]

0=85,8,x7C003478,x00000352

which unfortunately doesn't work anymore. Obviously I make a mistake here but I have no clue how to work around this. Is there another way to do this, I do not want to assign a button just to "switch on" the ground effect? I'm not a programmer otherwise its much easier to write a program for this I assume :?

Chris