Jump to content

TimRobertsen

Members
  • Posts

    220
  • Joined

  • Last visited

Everything posted by TimRobertsen

  1. Could that mean that the early Hornet-stick was intended to function similar to the F-16s stick? I.e. the stick had almost no movement; the input was measured in force instead of stick-travel. The planes are siblings, of a sort The younger, less extreme, half-brothers of the space shuttle Glad to see that they had to add some curvature to the roll-input I can feel less bad about having the curvature set to 40 in DCS
  2. For the last couple of days DCS keeps crashing/freezing whenever I'm in the Controls-page in Options. Within 10 seconds of entering the controls-page, it freezes up. The same crash happens regardless of whether it from the meny or in-game. Any idea whats going on?
  3. AoA is a result of A/C-weight/aerodynamic loading: turning, airdensity (altitude) and airspeed You don't even need altitude in the equation, as IAS already accounts for airdensity This is atleast my understanding of aerodynamics It could be wrong, I do have flaws Sometimes you need A/B for ideal flight. F.ex. ideal climb-speed, set on FPAS-page. With a max-loaded Hornet, you will not be able to achieve the ideal climb-speed without A/B.
  4. It does work, to some degree. If you set the ATC when you are at a steady attitude, preferably 0 to 3 degrees down. The aircraft usually does a dive when ATC is initiated, but once you correct for that (by flying pitch with the stick), it starts to do a sluggish kind of job:p It seems that the "AOA-lock" is decoupled/lost with ATC engaged. The aircraft acts more like it's landing/flying with the flaps in auto. The ATC-landing actually works fairly good if you're doing a flaps-auto field landing.
  5. FPAS is the best page!
  6. I thought it was standard to switch to "standard atmosphere" at 10.000ft.
  7. Heheh! The love for aviation brings people together!! That was quite a comprehensive list! Throw up the F/A-18-list, I dont know too much spanish, but google transelate knows a lot
  8. Cool! I'll check it out Once I got into coldstarts, I made my own startup-checklist and tried to make as complicated as possible As you said earlier, it's a great way to get familiarized with the cockpit and the systems.
  9. Heheh! Sorry, I neglected to mention in that post that I got it to work as I wanted, with your help You have my many thanks Yeah, but it's weird how one can become overly fixated on a side-aspect of a game/sim Once I started looking into cold-starting I fell into a rabbit-hole It was all I did for a month (maybe, atleast a couple of weeks )
  10. Same here I just keep thinking that there must be a way to do it The triggers are listed in the "mission.lua-file" within the .miz-file. So there must be a way to copy them and put them in their own trigger-script-file. It's just a matter of how to do it
  11. I was acutally looking for having a cold cockpit to be even colder, ice cold startup So that I could do my unnecessarly long startup-list It's not a cold start if it takes less than 15 minutes Edit: Got it to work as I wanted with the help of Rudel_chw
  12. Do you know if it is possible to make a script which can run the different clickable actions? So that you can simply have a trigger to run a script, instead of having to set up a long list of actions.
  13. Makes sense (now that I am aware of the fact:p) I got everything to work as I wanted Thanks for all the help! My new F/A-18 trigger-list: Strobe Down 8 3009 -1 L Gen off 3 3028 0 R Gen off 3 3029 0 -Axis- UFC bright 25 3040 -1 x50 Comm1 Vol 25 3036 -1 x50 Comm2 Vol 25 3038 -1 x50 Oxy flow 10 3004 -1 x10 Ifei Bright 33 3008 -1 x40 Defog Handle 11 3015 -1 x130 Cabin Temp 11 3017 -1 x15 Suit Temp 11 3019 -1 x15 Push to Test 30 3002 -1 x2 I'm surprised how easy it was, once I knew what to do and how to do it
  14. I've found that staring intently at the velocity vector does the trick both pre-contact and during connection. And let the periferal vision "anchor" you to the tanker. It worth keeping in mind that when you increase engine power (to increase speed), even just the slightest, the aircraft will start to pitch up, and vice-versa with decreasing engine power. Also, if you pitch up you'll start to lose speed, and vice-versa with pitch down. A/A-Refueling is a dance ... a dance with gatling guns, and rockets, and diesel
  15. It seems that all the different articles I've been reading on this subject have not been applicable to setting up triggers in the F/A-18. For ex. this one: http://volatusvirtualis.blogspot.com/2019/09/dcs-advanced-mission-editor-concepts.html In the Mirage there is apparently a correspondence between the "COMMAND" and the "PTN_XXX"-number in the clickabledata.lua. This does not seem to be the case with the F/A-18. As you point out: you have to get the command from the Options-Controls-page. Also, there is a difference between what is described in the "Cockpit Triggers"-doc and the F/A-18s Clickabledata.lua. F/A-18s Clickabledata.lua does not have “device_commands.Button_n”. It simply gives you an "element-number", which seems to not be usefull for the "COMMAND". No wonder I was confused. So, all in all: My bad! I assumed that the method for finding the correct "COMMAND" would be the same between aircrafts, which was not the case.
  16. Do the "pnt_234" (f.ex.) in clickabledata.lua have no function when it comes to setting up a X: COCKPIT PERFORM CLICKABLE ACTION-trigger? I've read a couple of places that adding "3" in front of the pnt_-number (f.ex. 3234) gives you the COMMAND-number you want for a given switch to use when setting up a trigger. To me, this does not seem to be the case. Or, there is a difference between airplanes. Most of the examples I've read have been with the Mirage (for some reason) I'm reading this in the future XD
  17. Thats odd, I'm not getting that info when I hover over any of the input-boxes. Is there some kind of a box to tick off to get additional information? This is all I get:
  18. Huh! Interesting! Where did you get Command 3003 from? According to the Clickabledata.lua, it is supposed to be 49, ei 3049. No conditions? Let's say I have several aircrafts/groups of client aircrafts, and I want a different setups, how do I get the different triggers to only affect specific aircrafts?
  19. I’m trying to set up the trigger, but I can not get it to work. I must be doing something wrong. In this simple case, I’m trying to have cockpit setup up a bit differently from the usual cold-start in an F/A-18, but nothing happens. I thought I’d start simple, so in the attached image I’m making a simple attempt at having the Master Arm switch set to Arm… but no luck. I’ve tried varies different Triggers, Conditions, Values, Devices, Commands. Any idea of what I am missing?
  20. This might have been posted before, but it I couldn't find any info. Is it possible to change the default/starting settings of the different switches/setup in the cockpit. For example: Strobe Light position to Off, Oxygen to Off. Comms volums. UFC brightness. Left/right Gen. Off. Defog Handle. ETC. Specifically for making missions, and having the different Clint-crafts with a pre-configured cockpit-setup.
  21. The track is a bit long, but it demonstrates the instant sound-travel. It's a bit interesting as, as far is I can see (hear), every other sound is modelled with correct sound-delay.
  22. About 9-9,5 degrees down (path vector/velocity vector), thats pretty much it. Any speed you want
  23. A bunch of info in that one
×
×
  • Create New...