• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Revisiting the Cloud 9 Phantom porting issue..

-For those who adopt ARS4 radar, I have replaced the Switch icon ARS by the icon of the radar gauge Phantom_X knob, allowing the window to popup Radar ARS4 in one click (1)
-Question: What is a LED (2) lights a few seconds after take off and retact the landing gear!
good day!





Alain

-
 
alain0568 said:
(...) -Question: What is a LED (2) lights a few seconds after take off and retact the landing gear! (...)
Click to expand...

The left one of the 2 red lights is the low altitude warning, it comes on when you are airborne, gear up and flying lower than the radar altitude decision height. There is a knob on the radar altitude meter to adjust the decision height, default is 200 feet AGL.

The right one of the 2 lights is the pull up warning which comes on if you fly below 500 feet AGL and your sink rate is over -3,000 feet/minute.

BTW: Both F16 and ARS4 radars can be switched on/off with the VC mode knob and the range can be adjusted with the VC range knob:
 

Attachments

  • C9_F4_ARS4.jpg
    C9_F4_ARS4.jpg
    44.2 KB · Views: 9
Both F16 and ARS4 radars can be switched on/off with the VC mode knob and the range can be adjusted with the VC range knob
Click to expand...

What are your panel settings please to do this with the ARS4?

Thanks!
 
expat said:
What are your panel settings please to do this with the ARS4?

Thanks!
Click to expand...

Hi Expat,

in the panel.cfg file you should activate the following:

;RADAR OPTION 2: Dietmar Loleit ARS4 radar
gauge50=ARS4!ARS_4, 378,203,248,242
gauge51=Phantom_X!Radar_Mode_switch_ARS4, 646,369,55,55
gauge52=Phantom_X!Radar_Range_switch_ARS4, 723,312,41,36

Don't forget to change the numbering of the gauges!!!

Ajustments are then made according to the photo in Henk's post.

Does this help?

Dumonceau
 
Last edited:
zsoltquack said:
The Cloud9 F-4 Phantom Portover kit v1.00.Ip package, the TuFun new AB effect work?I tested, but the AB radiation angle is not good. Any idea? :dizzy:View attachment 8347
Click to expand...
TuFun said:
Looks inverted... instead of going down it's going up. I'll grab the v.1 and do a test to see if that happens also.
Click to expand...
TuFun said:
I went ahead and resurrected FSX for testing purposes and found no issues with the v.100.You may want to check to see if the these lines in the [lights] section of the aircraft.cfg file are the correct numbers. [lights]light.9 = 9, -16.4, -2.25, -3.40, fx_F4E_C9AB ;MOD, classic engine burner 1light.10 = 9, -16.4, 2.25, -3.40, fx_F4E_C9AB ;MOD, classic engine burner 2
Click to expand...

Hi gents, I'm a lurker here. I mostly keep to myself, but I see a chance to help out here.

I had the same problem as zsoltquack with the diamond flame cones angled up instead of down.

The problem is in the effect files fx_F4E_C9AB_N.fx and fx_F4E_C9AB.fx.

If you open the files in notepad, you will see starting at the [Emitter.1]//----------------Diamond A2 entry, the line at the Y Offset=-0.20 ,-0.20 //----------offset from zero datum.

If you look closely at the comma placement.

The way it is (no space between the comma and the -20, i.e Offset=-0.20 ,-0.20.

The comma crowding the -20 on some systems sees it as a positive number. Basically the - is ignored.

It should look like this Offset=-0.20, -0.20

I went trough all the entries within the fx_F4E_C9AB_N.fx and fx_F4E_C9AB.fx and corrected the comma and all is working normally now.

Hope this helps, and thank you to all involved for making this work in FSX

Good day to you all

BB.
 
Last edited:
I checked the beta 1 and beta 5 and they have the same comma placement. The fx_F4E_C9AB_N.fx is the night AB which is bright white flame. The fx_F4E_C9AB.fx has the correct comma placement. I surprised no one mentioned this as these betas have been out for weeks. Test fine in FSX.



"The comma crowding the -20 on some systems sees it as a positive number. Basically the - is ignored." Thanks for this info. So that's what may have happened to others.

I'm uploading a Phantom X airshow and the AB effects is normal even with the comma spaced. Kinda interesting... the video is using the C9AB effects. :)
 
TuFun said:
I checked the beta 1 and beta 5 and they have the same comma placement. The fx_F4E_C9AB_N.fx is the night AB which is bright white flame. The fx_F4E_C9AB.fx has the correct comma placement. I surprised no one mentioned this as these betas have been out for weeks. Test fine in FSX."The comma crowding the -20 on some systems sees it as a positive number. Basically the - is ignored." Thanks for this info. So that's what may have happened to others.I'm uploading a Phantom X airshow and the AB effects is normal even with the comma spaced. Kinda interesting... the video is using the C9AB effects. :)
Click to expand...

Oh dear, sorry, I copied and pasted from the file as so I wouldn't make any mistakes, and did anyways.

Yes the same problem in the fx_F4E_C9AB.fx, but just in the Diamond section of the fx file.

Just correct the comma placement and all is good.

Sorry for the mistake, we are just humans.


Good day again to all

BB,
 
Bunker_Buster said:
Oh dear, sorry, I copied and pasted from the file as so I wouldn't make any mistakes, and did anyways.

Yes the same problem in the fx_F4E_C9AB.fx, but just in the Diamond section of the fx file.

Just correct the comma placement and all is good.

Sorry for the mistake, we are just humans.


Good day again to all

BB,
Click to expand...

Yep, you are right... space comma... and still normal AB in my case. Wish someone would have caught this in beta1!

Thanks again for the info... much appreciated. TF
 
TuFun said:
Yep, you are right... space comma... and still normal AB in my case. Wish someone would have caught this in beta1!

Thanks again for the info... much appreciated. TF
Click to expand...


I just checked the fx_F4E_C9ABU.fx file and it has the same problem, but only in the Diamond section of the fx file, I believe this is the smokeless fx which I don't use.

This comma placement is a real pain with some systems, for reasons I don't really understand. but it can make one very annoyed trying to find it.


Good day once again.

BB
 
Just curious... I'm using Acceleration. Wonder if SP2 users is having the problem or just don't matter if ACC is install or not.

I informed Henk about this situation.
 
Not sure, I have FSX Gold with acc installed, I think it is something to do with the OS / system.

May have to do with the version of MSXML & MSV C++ running.

I'm not a computer expert, but I do know the text format is key in a lot of coding.

In order for the FX engine to read the data it must be formatted so there is a space after the comma to separate the parameters. When crowed like this '-

The - is not seen properly.

Wrong Y Offset=-0.20 ,-0.20 Correct Y Offset=-0.20, -0.20

I always just separate each element like this Y Offset = -0.20 , -0.20 so its clear to be read.

Note the - must be close to the numbers with no space. If you put a space there, it becomes a positive value.

Also wrong Y Offset = - 0.20 , - 0.20 Correct Y Offset = -0.20 , -0.20


Good day

BB
 
I did a text search and replace on all 3 fx AB effect files (not using smokeless) and found a number of instances with a space before the comma. All were the same parameter of Y offset, but with different components.
 
Bunker_Buster said:
Not sure, I have FSX Gold with acc installed, I think it is something to do with the OS / system.

May have to do with the version of MSXML & MSV C++ running.

I'm not a computer expert, but I do know the text format is key in a lot of coding.

In order for the FX engine to read the data it must be formatted so there is a space after the comma to separate the parameters. When crowed like this '-

The - is not seen properly.

Wrong Y Offset=-0.20 ,-0.20 Correct Y Offset=-0.20, -0.20

I always just separate each element like this Y Offset = -0.20 , -0.20 so its clear to be read.

Note the - must be close to the numbers with no space. If you put a space there, it becomes a positive value.

Also wrong Y Offset = - 0.20 , - 0.20 Correct Y Offset = -0.20 , -0.20


Good day

BB
Click to expand...

Very interesting... thank you! I was using the standard protocol, never thought about this one... Y Offset = -0.20 , -0.20

I've sent Henk the updated AB effects.

Update #2: https://app.box.com/s/k9x80wxzc2y37w4nco7z

Before... AB rings in the nozzle flaps (turkey feathers).

View attachment 8402

After...

View attachment 8403
 
Last edited:
WarHorse47 said:
I did a text search and replace on all 3 fx AB effect files (not using smokeless) and found a number of instances with a space before the comma. All were the same parameter of Y offset, but with different components.
Click to expand...


That is normal, each emitter has a different y offset to angle down the diamond flame cone.

The y offset shifts the emitter up or down from the fx center line.

The x offset shifts the emitter right or left of the center line of the fx

It all works in conjunction with the z offset that spaces the emitters apart fore and aft.


Good day

BB
 
You must log in or register to reply here.
Back
Top