• 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.

HU: Seems that Cerasim released new helicopter AS365N3

Hi does anyone know how to colour in green the upper plexiglass in order to be visible from outside view? I can do this only from inside. Thanks
 
It is not possible - the Developer use only one glass-texture for all windows. Intern glass-textures are splitted and so it is possible to give them an other color .

ATB

Dirk
 
Hello,
My name is Tino Broekstra and I am owner and chief editor of the Dutch FS related website www.fsvisions.nl
In Prepar3D I do fly most of the times with helo's and the AS365 is one of the helo's I do use.

I do have a question about the usage of the TSS Dauphin sound package, I used to use wit the AlphaSim Dauphin.
When I install the TSS sound into the CeraSim Dauphin, I get a repeatingly startup sound. This will continue as long as I do fly the Dauphin, so it will never stop.
I asked TSS if there is a solution, but sad.ly they don't answer my mails.
Does anyone here at the SOH fourms know how to get the sound into the CeraSim Dauphin?

Thanks in advantage.

Tino
 
I have an all new sound system specifically designed for the Cerasim AS365 as well as the older FS2004 freeware models. I am currently reworking the FDEs for the Cerasim bird to give a longer rotor startup and spooldown. Give me some time to get these finished up and I'll upload the package. And yes, it sounds like the real deal ;)
 
I have an all new sound system specifically designed for the Cerasim AS365 as well as the older FS2004 freeware models. I am currently reworking the FDEs for the Cerasim bird to give a longer rotor startup and spooldown. Give me some time to get these finished up and I'll upload the package. And yes, it sounds like the real deal ;)

Sounds fine to me :)

Does this mean, the TSS sound is not going to work with the CeraSim bird?

If you need someone to test the FDE and sound system, please feel free to ask ;)

Please keep me in the loop concerning your package and when it will be available for download. I will mention the release also on my website if you agree.

Tino
 
They released a patch! Now nose wheel, altimeter, and rotor motion are fixed. Also sound and textures have been tweaked a bit
 
Where does one get the patch. I checked my FS PilotShop account and no download for the patch. The original download still says version 1. ????
 
I got an email from Simmarket where I bought the product. Probably PilotShop will send you an email soon? Frankly I don't know
 
for those using the HTR profile for the as365:

the model forces 'on' auto-coordination > 40kias and forces it 'off' <40kias. this results in abrupt yaw action at the transition point which is rather annoying and requires constant pedal input at slow speeds.

as this is an aircraft equipped with sas/afcs, it should be stable and hold heading without pedal input when main rotor torque is constant.

so, to get around this, you can edit the psystem.xml file in the \Panel\CSAS365\ folder.


*** make a backup or the original psystem.xml file before editing ***

1) open the psystem.xml using notepad
2) do a string search on "(A:AIRSPEED INDICATED, knot) 40 >" this will be at the tail end of the file
3) change the section

from
Code:
(A:AIRSPEED INDICATED, knot) 40 > if{ 1 (>L:autocord, bool) } els{ 0 (>L:autocord, bool) }
               (L:autocord, bool) if{ (A:AUTO COORDINATION, bool) ! if{ (>K:AUTORUDDER_TOGGLE) } }
            (L:autocord, bool) ! if{ (A:AUTO COORDINATION, bool) if{ (>K:AUTORUDDER_TOGGLE) } }
to
Code:
(A:AIRSPEED INDICATED, knot) 40 > if{ 1  (>L:autocord, bool) }  }    <!-- //els{ 1 (>L:autocord, bool) }   // --> 
<!-- //    (L:autocord, bool) if{ (A:AUTO COORDINATION, bool) ! if{ (>K:AUTORUDDER_TOGGLE) } }// --> 
<!-- //    (L:autocord, bool) ! if{ (A:AUTO COORDINATION, bool) if{ (>K:AUTORUDDER_TOGGLE) } }// -->
then save the file.

this change will force auto-coordination 'on' only when ias is > 40kias but you can also turn 'on' auto-coordination with a key stroke (or key assigned to hotas) at lower speeds. as a bonus, HTR users can turn on autohover by turning on/off/on auto-coordination as described in the HTR manual.

After this change, auto rudder is disabled, but nothing will automatically be enabled above 40 kias, because L:autocord is set, but never used. At least I did not find any other references in the panel or model.

What should happen above 40 knots?
 
After this change, auto rudder is disabled, but nothing will automatically be enabled above 40 kias, because L:autocord is set, but never used. At least I did not find any other references in the panel or model.

What should happen above 40 knots?

this is for using htr with this model--when htr is used, one would turn on autocoordination (via realism menu, key press, or in my case, key mapped to hotas) to simulate afcs. the mod to the xml above is to prevent autocoordination from being disabled when going below 40kts.

also, when the autocoordination key is double clicked, it will allow autohover.
 
this is for using htr with this model--when htr is used, one would turn on autocoordination (via realism menu, key press, or in my case, key mapped to hotas) to simulate afcs. the mod to the xml above is to prevent autocoordination from being disabled when going below 40kts.

also, when the autocoordination key is double clicked, it will allow autohover.
Ah, I understand ... so the plan is that nothing should happen at all, in which case the smallest required edit is to add <!-- before and --> after the code block:
Code:
<!--
                        (A:AIRSPEED INDICATED, knot) 40 > if{ 1 (>L:autocord, bool) } els{ 0 (>L:autocord, bool) }
                        (L:autocord, bool) if{ (A:AUTO COORDINATION, bool) ! if{ (>K:AUTORUDDER_TOGGLE) } }
                        (L:autocord, bool) ! if{ (A:AUTO COORDINATION, bool) if{ (>K:AUTORUDDER_TOGGLE) } }
-->

(I'm a big fan of small changes, because they make it more clear what actually happens, and they are easier to add/remove :))

By the way, thank you for your VC mod and the HTR profile, this is a very helpful addition for this helicopter!
 
Ah, I understand ... so the plan is that nothing should happen at all, in which case the smallest required edit is to add <!-- before and --> after the code block:
Code:
<!--
                        (A:AIRSPEED INDICATED, knot) 40 > if{ 1 (>L:autocord, bool) } els{ 0 (>L:autocord, bool) }
                        (L:autocord, bool) if{ (A:AUTO COORDINATION, bool) ! if{ (>K:AUTORUDDER_TOGGLE) } }
                        (L:autocord, bool) ! if{ (A:AUTO COORDINATION, bool) if{ (>K:AUTORUDDER_TOGGLE) } }
-->

yes, should work, too, commenting out whole section w/ <!-- -->. be sure to make a backup to the original.
 
Good day,

Digging this one up in pursuit of a livery - also in light of the fact that the Dauphin is now compatible with P3D4.2 in addition to the existing FSX product.

I see a German Notarzt livery in black, red, and white featured in post #59 earlier in the thread from a couple years ago now (as posted by Rebo). Is it possible to make this available to the public?

Additionally, considering the fact that Aussiex.org is still down unfortunately, are liveries hosted there available anywhere else? To add to this aussiex inquiry, have those liveries been updated to reflect the paint mapping adjustments from the patch as of a few months/year ago?
 
Back
Top