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
Does this chopper work in P3D v3.4?
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![]()
Does this chopper work in P3D v3.4?
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
toCode:(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) } }
then save the file.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) } }// -->
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?
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: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.
<!--
(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) } }
-->
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) } } -->
All my Repaints are updated and available now - they fit the new textures after the patch now.
D-HNHD : https://www.dropbox.com/s/jy7wwxwv6rgb3qu/texture.DHNHD.zip?dl=0
D-HOIT : https://www.dropbox.com/s/qpxg3jzq339z3gz/texture.DHOIT.zip?dl=0
D-HATD : https://www.dropbox.com/s/m7bs0xxyxkt1wla/texture.DHATD.zip?dl=0
ZJ871 : https://www.dropbox.com/s/83uxkk8pgmtovz2/texture.ZJ781.zip?dl=0
XY863 : https://www.dropbox.com/s/5hbjvx3w2xjz5cd/texture.XY863.zip?dl=0
ZJ183 : https://www.dropbox.com/s/too30foxgx1hggl/texture.ZJ183.zip?dl=0
OO-NHN : https://www.dropbox.com/s/bzaedh8w3t8fysk/texture.OONHN.zip?dl=0
OO-NHV : https://www.dropbox.com/s/o3avav7e99cf1am/texture.OONHV.zip?dl=0
OY-HTH :https://www.dropbox.com/s/g8j54ahcoh3mmfc/texture.OYHTH.zip?dl=0
G-HPDS: https://www.dropbox.com/s/p5j4ic47x3i4ihy/texture.GHPDS.zip?dl=0
N964TT: https://www.dropbox.com/s/v1bl5o7mgh5xb7c/texture.N964TT.zip?dl=0
CC-CLP: https://www.dropbox.com/s/18e1hwo8y7fx58w/texture.CCCLP.zip?dl=0
F-GYPD: https://www.dropbox.com/s/9jwcp0qx7x51j6f/texture.FGYPD.zip?dl=0
GreetingsDirk