Bell 412

[valery]

Thanks Sanhozay.
It seems that ALS don't allow true location/pos, which is really useful to me here (the Bell spotlight is moving and can be extended or retracted), but it will be ok. Trying it ...

[IAHM-COL]

beautiful work, valery!

[Octal450]

simply amazing

[valery]

well, pleasure is mine itOutchpod !
Lights are done, very difficult and annoying with FG ... (2 rendering systems, many ways, docs not always clear and user-friendly ...). After all this work on lighting, I think it's better to do the job yourself with your own shader. next time.

Well, now going back to the FDM before evolving (or trying to) the AFCS for the Bell (SAS ..)
FG/Docs/ provides a file : README.yasim.rotor.xls
Its purpose is to provides 3 VBA functions in order to choose your Yasim parameters that match your Airfoil data.
The problem is: where is the xls function module ? using the spreadsheet lead to a #NAME error because the VBA module is missing (or void)
So, I tried to write these VBA "fuckng missing" functions from the cpp Yasim source files, and I got them.
But it is still a parameter that is not Ok for me (the "incidence" parm to be accurate). Don't know what the Yasim author expect (and this is not the AOA).
Simple question: does anyone have a valid xls file including the VBA module with the 3 missing xls function ?
(thanks in advance to don't ask : hey dude, why you don't use JSBSim ...) Grrrr

Thanks,

Val.

EDIT: ok, got it:
The 2006 version is Ok:
https://sourceforge.net/p/flightgear/fg ... format=raw

CU

[valery]

Hello everybody,

a small (at a very poor quality ) video that show you the last improvments and how to start the chopper:
https://www.youtube.com/watch?v=nfULqEnYjU0

v0.4 near to be done. I'm re-writing the whole engine system (n1/n2/gearbox/transmission/fuel cons./air density ..) in order to have a true OEI behaviour (One Engine Inoperativ), and a realistic instrumentation and limitation. A lot of physics (and I'm very bad with this) and headhaches ... but still funny.

CU

Valéry

[Octal450]

Valery, excellent work!

[valery]

Thanks itOuchpods, I really appreciate your comments.

Now a bit of funny things: FG being not a very dev-friendly app (start, try, quit, start,try, quit,....), I was tired to restart it every time I need to test my nasal engine model (but perhaps it comes for my small noobs experience with it). So, I make the engine model for Processing, and "voilà" the PT6T Turbine running :

https://www.youtube.com/watch?v=yiDhiwz6G00



Tell me If you see something wrong or perhaps misunderstood from me.
Step are described in the "video comments".

Next to come: 2cd Turbine + CBOX ; the Processing sketch will be included with the next Bell version.

Thanks for your help,

Val.

[Octal450]

Wow. That's cool!

[IAHM-COL]

the vid looks great. I just havent figure out what I am looking at yet.
Are you saying you are doing nasal to work outside fg so you can develop easier?

[valery]

No, it's not a nasal script, but a Java one using http://processing.org/ renderer. It's all about classes and members, so no big troubles to translate from one language to the other. I'm using some extended ease functions to interpolate my values. I will put them to my nasal in order to replace some "interpolate()" calls, so others can use them (FG use a linear interpolation, and it seems that the dev. have forgoten to add the whole "ease" mess : http://easings.net/).
With FG, IMHO you cannot reload your Nasal scripts, so you have to restart it every time you need to see your nasal modification. It was really annoying and fastidious for me.
In the previous Bell version, the engines were simply simulated. With this new one, they are modelized, so the Bell will loose power at hi alt according to AOT/Pressure/..., it can operate in OEI mode, N2 depends on the power of N1 which depends on the needs of N2, etc...
I found out some data on the PT6T-3D engines, but I' not sure how it really works (especially the way it works in OEI, because a single shaft in OEI seems to produce more power than it theorically can), so sometimes I deduced some behaviours from what I saw on the net. This is where I need help !
FYI, the processing sketch will be part of the next version, so you could see by yourself.