Jump to content

StandingCow

Members
  • Posts

    1990
  • Joined

  • Last visited

Everything posted by StandingCow

  1. I know you can adjust the seat with shortcut keys, but does HB ever have plans to make the switch in the cockpit work? A few patches ago we think the pilot position changed and is high up now, which makes refueling pretty difficult, it's easy enough to use the keybinds, but it would be really nice to be able to use the in cockpit switch. Any HB plans to make this functional?
  2. Per the bug report section there is def something goofy going on with it, for one the elevation is possibly backwards. But aside from that being able to see an entire vehicle in the TADs but the radar can't see it seems wrong as well.... so I'd say it seems a bit 50/50 atm.
  3. Does this mean that we will be able to return defective units there instead of back to China? If so that is even more fantastic!
  4. Between me and my flight mate we have had this randomly happen to each of us with no rhythm or reason.
  5. Having this same issue, changed a bunch of graphic settings but nothing got rid of it.
  6. Same exact for me. I think It's supposed to be like this and whoever did the promo video for WW thought the same as we did.
  7. Yea, got mine and I have to say I agree with the disappointment of the parking brake lever not operating like in the video.
  8. Nice, I ordered one the other day, should be here next week. Gotta get some slotted aluminum and the drill out to mount it.
  9. DOLT flight is looking for folks that would like to join us on a Foothold campaign this weekend (Saturday and Sunday) starting at 12 AM ET - 4 AM UTC - 12 PM AWST - 2 PM AEST. All skill levels are welcome, we enjoy training folks that are new to the game so don't be shy if you aren't sure what you are doing. The DOLT flight motto is, "REX EST LUSCUS" comes from "In the land of the blind the one eye'd man is king.". Your average DCS player may suck, we like to think we suck SLIGHTLY less. So, you know what you are in for. Discord link: https://discord.gg/QMmQkRAb?event=1101004291101180036 Server details will be in the discord.
  10. Newy, wrong file. This is dots.fx. Can ED at least improve the dots before removing our ability to alter them? Maybe implement the mod as a permanent change so that playing at a higher resolution isn't a negative?
  11. It's pretty hilarious that this doesn't break IC... but I am also glad it doesn't so that the community can fix what ED has been seemingly ignoring.
  12. Ok, this is fixed, Thanks to a suggestion from Special K in the discord I moved the MFDs to the right of the screen instead of under it. Works with the default ED file now. The George AI must have been hiding under my displays due to the resolution going downward.
  13. Hey all, I recently moved to a cockpit that is separate from my other monitors (in different rooms). I haven't been able to figure out how to get my George interfaces to show up though. Here is the display setup: monitor.lua file: _ = function(p) return p; end; name = _('Cockpit'); Description = 'Sub Displays' Viewports = { Center = { x = 5360; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; } } LEFT_MFCD = { x = 5360; y = 1440; width = 525; height = 525; } RIGHT_MFCD = { x = 7395; y = 1440; width = 525; height = 525; } F14_JESTER_MENU = { x = 5360; y = 0; width = 2560; height = 1440; } GU_MAIN_VIEWPORT = Viewports.Center UIMainView = Viewports.Center George AI file: --viewports stuff local v = find_viewport("GU_MAIN_VIEWPORT", "CENTER") if v ~= nil then if v.width ~= total_w or v.height ~= total_h then ULX = v.x ULY = v.y SZX = v.width SZY = v.height local aspect = SZX/SZY local offsetX = (ULX + SZX / 2 - total_w / 2) / total_w * total_aspect * 2 local offsetY = -(ULY + SZY / 2 - total_h / 2) / total_h * 2 local padding = math.min(total_aspect, aspect) * 0.2 compass_pos = { -math.min(total_aspect, aspect) + offsetX + padding, -1 + offsetY * 2 + padding} weap_control_pos = { math.min(total_aspect, aspect) + offsetX - padding, -1 + offsetY * 2 + padding } compass_size = compass_size * v.height / total_h weap_control_size = weap_control_size * v.height / total_h end end --end viewports stuff Any help would be appreciated!
  14. Agreed. Thanks for your help. Hopefully one day I can switch to Helios as it does seem to be the better way to do what I am doing. I guess I'll have to deal with the black screens.... but the George AI display not working is a real issue.
  15. ED please.... before you implement something that breaks current user created tools... ED needs to supply us with something equal or better.
  16. Does helios break pure script servers though? I fly primarily MP so don't wanna do that if it's avoidable. Hopefully ED eventually allows access as requested here:
  17. Greetings folks, I was hoping someone would be able to help with some questions I have. My set up is my main monitor (set as primary in windows) and a left monitor are in my office, these are no longer used for DCS. My TV and MFDs are part of my cockpit setup in another room. Currently everything is working but the way I have it set up... my 2 office monitors have a black screen (since I am stretching DCS's display out). Is there a way to set this up without having to do that? Or without having to set my TV in the other room as a primary display? I've attached a graphic showing my displays as well. Here is my currently monitor.lua file: _ = function(p) return p; end; name = _('Cockpit'); Description = 'Sub Displays' Viewports = { Center = { x = 5360; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; } } LEFT_MFCD = { x = 5360; y = 1440; width = 525; height = 525; } RIGHT_MFCD = { x = 7395; y = 1440; width = 525; height = 525; } F14_JESTER_MENU = { x = 5360; y = 0; width = 2560; height = 1440; } GU_MAIN_VIEWPORT = Viewports.Center UIMainView = Viewports.Center I am also having issues with my current config getting George AI to show up in the Apache. I've been following that thread --viewports stuff local v = find_viewport("GU_MAIN_VIEWPORT", "CENTER") if v ~= nil then if v.width ~= total_w or v.height ~= total_h then ULX = v.x ULY = v.y SZX = v.width SZY = v.height local aspect = SZX/SZY local offsetX = (ULX + SZX / 2 - total_w / 2) / total_w * total_aspect * 2 local offsetY = -(ULY + SZY / 2 - total_h / 2) / total_h * 2 local padding = math.min(total_aspect, aspect) * 0.2 compass_pos = { -math.min(total_aspect, aspect) + offsetX + padding, -1 + offsetY * 2 + padding} weap_control_pos = { math.min(total_aspect, aspect) + offsetX - padding, -1 + offsetY * 2 + padding } compass_size = compass_size * v.height / total_h weap_control_size = weap_control_size * v.height / total_h end end --end viewports stuff
  18. Take your time and do it right fellas. We know HB puts out quality products.
  19. Nice, hopefully ED can investigate and find the cause. Anything to help MP performance is a win for everyone.
  20. What's the effective range of the A and B missiles now? I know it depends a lot on altitude, speed, etc but vs an aim120c how much extra range do you think we will get out of each missile now?
  21. Are the vehicles that are the wrong color for the mode freshly spawned in by chance? A buddy and I noticed that freshly spawned vehicles, even if moving, take a while to warm up.
  22. Yea, it feels like sometimes threads are marked "correct as is" without much thought, not saying that's what is actually done but it feels like it. That thread you linked could possibly be related to this "issue" if it is actually even an issue, hard to know. And before this thread was marked correct as is... was the team asked about it? Was the f16 tested with the fuel door open after the FM changes? So many questions...
×
×
  • Create New...