Jump to content

CrimsonGhost

Members
  • Posts

    298
  • Joined

  • Last visited

Posts posted by CrimsonGhost

  1. Hello all. I’m gonna go ahead and be that guy. :cry:

     

    Would anyone have a recently updated SP shooting range/training zone mission that they may be willing to share? The last one I have is Vipers 1.5 Range that I have butchered into an unrecognizable mess with my poor mission editor skills. :doh:

     

    I know it’s awrully early but inclusion of the Tarawa and KC-130 would just be amazing. This would give me a couple more ways to wreck even more Harriers. :D

     

    I also know this is a big request. I can’t be the only one that could really use the assistance of some of you more talented mission designers. Thanks

  2. Hey Mirknir. Sorry to hear you are becoming burnt out, but I completely understand. As you know I used to really enjoy your server. However with the recent change in direction you mentioned I just can’t bring myself to log in. I miss the good old days where you could actually do something other than air quake, or get shot down by the air quakers.

     

    I had a thought/idea a while back that while it would be wholly unpopular, could be interesting. That idea was to completely remove, or disable, all of the slots for the aircraft that are usually used in air quake scenarios. I can hear the screams and rage generated by those reading this and while I am sympathetic, there are other servers more suited to this. OC used to be a great place to come in and learn a new module and have a great time.

     

    Anyhow, I know I will not make any friends with my suggestion, but it’s just an idea. Maybe one day I will get around to figure out how to run my own server. I have the hardware and bandwidth, but not the knowledge to make it happen.

     

    Again, not looking to step on anyone’s toes or hurt anyone’s feelings. Just spitballing an idea. Thank you Mirknir for all the work you have done for the community. I know I will support whatever direction you choose to go with OC.

  3. Your doing great work on this server Mirknir. Personally I have not been on the server much as it’s always full. I am glad you are taking the necessary steps to prevent this server from turning into another air quake server. Some won’t like it, but they can go to those servers if they want that. Thanks again for all the work you do for the community.

  4. This round of Blue Flag has been tempting me to join. Still haven’t managed to land the Mi-8 quickly and reliably enough to feel confident that will actually help. I have watched some excellent streams of the action though.

     

    Quick question about the recon slots. Do they actually provide any information to the GCI or the rest of the team or is it just what is verbally passed on via SRS? If it actually helped I might actually have the nerve to hop in with the big boys. :)

  5. I just did a search for pretty much the same issue and rather than starting a new thread, I will ask here.

     

    My primary problem is when piloting the A-10C in the NTTR. Anytime there is sunlight on the panels, primarily the UFC and CDU, the markings on the panel are invisible. This makes use of either of these panels difficult at best. I imagine it’s something to do with the new lighting and have not posted about this until now as I was waiting to see what would happen. I figure it’s been long enough now to ask the question as I can’t be the only one with this same problem.

  6. Turning off fast align on the M-2000 wouldn t change "air quakers" ' mind

     

    there are almost no reasons to align the INS on OC :

     

    - the ground targets ( factory, listening posts... )' coordinates and altitudes are not given in the briefing, therefore, INS can not be used for a bombing run, which is sad and could be fixed....

     

    - there is the F-10 map, which is going to be used even with aligned INS, because INS is not GPS and doesn t let you know where you are unless you create several waypoints on the ramp.

     

    - aligned INS is needed to get the correct heading to display on the HUD, but there is a second rudimentary compass above the INS panel which doesn't require Alignement.

     

    That is why you won t prevent people from taking off in 2min if you "only" turn off fast align on the m2000.

    Therefore, even if defuelling a combat ready Aircraft is "unrealistic" on an advanced module, it is the way to solve the issue.

     

    Mirk, how difficult would it be to get Skynet to include MGRS or L/L when announcing targets?

  7. Hello all. I am in the process of building another PC and am very familiar with the archaic Deactivation/Activation system. However, as I keep my DCS installs on their own SSD, can I just move the drive to the new PC? I know I will need to transfer my settings and such, and of course go through the activation process with every module, but in theory I should be able to migrate the drive. Does anyone have any experience with this? :confused:

  8. Hello all. I am rather torn right now and not really sure which way to go. For a very long time now I have been flying DCS in 4K, and as most of you probably know, target spotting is painful at best. With no sigh of any changes coming to scaling, what would you guys recommend? I have the hardware to run pretty much any monitor configuration so that is not an issue.

     

    So which direction to go? I have been using a 48" 4K tv that I replaced 3 4K monitors with hoping to let me see targets better. I have a hard time going back to 1080p. Next option is to move to wide screen format. I have been looking at the Acer X34P. Is anyone running one of these, and if so, how is if?

     

    Thanks for the input and advice. I can't wait to hear your opinions.

  9. I can only share my experiences, but with the pitch trim bound to the trim hat on my Warthog the time it takes to make any change in trim is horrendous. For instance, going 3 degrees nose up for take off with the XT tank, averages 30 sec.

  10. Up to yesterday, the single pedal wheelbrake worked for me. Since differential braking is not really recommended for the Viggen, and it's a bit difficult to avoid unwanted differential braking especially during landing, I had assigned my right pedal to the "Wheelbrake" command and I'm fairly sure that was working. I have updated to the latest beta release and now it's not working any more, and I have to go back to separate left and right wheelbrakes. This is a bug.

    When the system works properly you should be able to bind just the left pedal to the "Wheelbrake" command.

     

    I double checked my binding after the update yesterday and it still does not work. Never has worked as others have posted. Still waiting on someone from LN to acknowledge that this is being looked into.

  11. The amount of light that the beacons cast on objects is very realistic. Granted I've never seen a Viggens lights in person, but working around airliners when this kind of light was common, the light splash looks great. But the lack of any light effect on the bulbs themselves is indeed a bug.

  12. Yep. It's the air passing through the engine becoming unstable, and if allowed to continue, it can destroy the engine. Worst I ever saw in real life was a 727 (JT8D engine that the Viggen's RM8 is based on) that when cleared on to the runway, the crew went immediately to takeoff power, rather than letting the engine stabilize first. End result sounded like a bomb went off with visible pieces of what used to be the #2 engine coming out the back of the engine, and a very abrupt aborted takeoff. I recall that one taking a long time to taxi back to the gate. :)

  13. I have my trim bound to the trim switches on my Warthog. While they do work, the movement is so excruciatingly slow that for a wile I believed it wasn't working. Try holding down the command and watch the gauge on the left side of the cockpit.

  14. I can't address all your concerns, but I can tell you what I know and give my opinion.

    The lack of a Flight Manual/Docs folder is a known bug and will be fixed soon.

     

    From what I have noticed so far, many of the rotary switches are not ones you have to manipulate very often. And when you do, it's not too difficult to move them with the mouse.

     

    Same thing goes for the TILS rotary, and the lights. The interior lighting is mostly controlled by the two potentiometers behind the throttle. Exterior lights are all controlled Buy 4 switches on the rear part of the right console. These again are easily manageable with mouse controls.

     

    Lastly, as far as I know, there is no control to engage/disengage the NWS. Wether this is a bug or working as intended, I do not know. If you find it a too sensitive, throw a curvature on the axis. Personally I have mine set to 19.

     

    I know these aren't exactly the answers you were looking for, but I hope they help. And in my humble opinion, you would need a full home cockpit to assign everything you mention to hardware. And keep in mind, this is just the very first early access build. Bugs will get squashed rather quickly.

  15. There was an announcement listing known issues that did not get addressed in time for the launch. One of the issues was that some joysticks that use twist grip for yaw are not working correctly. This may be a part of your problem.

  16. First off, like most everyone else, thank you for this great module. On to my particular issue.

     

    I fly with a TM Warthog and MFG Crosswind pedals. I know the normal scenario is to bind each toe brake to its respective wheel brake. However this does not work for me as I am an amputee and unable to use the right toe brake. I typically bind both wheel brakes to the left side as a compromise. Currently if I use the wheel brake binding there is no effect. I am curious if this is a bug or intentional.

     

    Side note, is there anything in the cockpit that provides a visual indication of brake activation? Normally we can see the pedals tilt, but not in this case.

×
×
  • Create New...