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
Use keys or buttons assigned to AileronTrim Left and Right commands.Deleting that camera view .015 worked and stopped the black screen.....
Now if I can just figure out how to rotate the engines........
Rick
I found this in the FS Developer forum:
Look at Post # 36 on the black screen issue
http://www.fsdeveloper.com/forum/threads/mv-22b-osprey-release-1-0.439626/page-2
Use keys or buttons assigned to AileronTrim Left and Right commands.
See last chapter of the Flight Manual .....
Rob
Use keys or buttons assigned to AileronTrim Left and Right commands.
See last chapter of the Flight Manual .....
Rob
I downloaded it and am learning it. I for one expect more from the members here as to their decorum. Developers put in a ton of hard work making aircraft, scenery, etc. When you disparage their work or them, you discourage them from doing further development. I know, I quit publishing my work for just those reasons. I think that Kalong, Rob, and all the other people that helped did a great job. It flies great, so what if some things are not working or not fixed yet. The people complaining the loudest probably still fly a bunch of FS9 portovers with 2D cockpits. You didn't pay anything for it so if you don't like it , don't fly it. There is no reason to make snide comments on a forum.
I just watched a 3D animation of an MV-22 crash due to VRS. You'd think with all the helicopter experts in the military that this would have been known and taught completely to the pilots of this rotor-wing a/c.
Hi all,
Finally I have permission to make a comment.
first. Thanks for donation.
second.
is there any "user" (sorry if it not right word) has experience crash / CTD? I need some data, like crash report, OS, and FSX/P3D version. I need to localize to make easier to find (actually hard), but I will try.
another issue I can gather is:
- blooming ( solved, see my main forum)
- stick, throttle texture problem, if can use self solving. describe on my main forum
- weird at initial / after load aircraft i.e. engine prop stop, this written on flight manual
- prop rotation stuttering.
recommendation.
- please read flight manual, I know (honestly) my self is too lazy to read (any add on) aircraft manual. just because this aircraft is too complex then need a manual for it. thrust me it faster than you make try and error.
- make a save flight for this MV-22B and open for next flight. with this, all initial will work as it should be, no matter it running engine, flying/cruising, folding etc all will work as it should be (some specific will saved). but this not perfect either, sometimes there still has an issue
- please saved always when in VC view. dll gauge won't initiated properly when VC view never open. ( manual already explain)
- if you didn't understand explain in flight manual, you can ask me or Rob. I not use English in daily basic. English is my third language. hope you understand my write, sentences, spelling and pronounce still awful.
just a comment
some will have difficulty flying the osprey. I know, this aircraft not user friendly aircraft. but it has a purpose. close to the real as I can. if you want aircraft that just push button and fly, that will not happen. please throw away my aircraft.
if referring to real flight manual (I have obsolete one) it will more complicated than it show in cockpit and manual. too many restriction, load engine, temperature, altitude, wind speed, etc. etc. all done with osprey in Sim is simplified from real aircraft (I never see the aircraft directly). with this simplified, FSX/P3D still can't handle all system that we are simulated for. me and Rob must make another way to break FSX/P3D limitation. actually this aircraft already break FSX/P3D limitation, hope you realize that. if not, it's OK for me
I have 8000 lines script for PFD, MFD, CDU and aircraft system exclude VTOL gauge and map gauge. I trying to make it frame rate friendly (with help from Naruto-Kun), IMO it work in C++, but map (from FSX GPS map) that not quite frame rate friendly. if you realize map display will same displayed if 4 screen open together. but for display other than map (it was C++ dll gauge) there can be customize and no frame rate hit. I ever try use each screen has different map, my frame rate from 20 fps drop to 5 fps.
one thing to know is dll gauge use every frame to display, read and command. setting SIM on frame rate target at UNLIMITED setting is not wise. use frame target to 30-40 is more than enough.
I still need your advice, a positive advice to make it better.
Best Regards, Maryadi