Jump to content

Eldur

Members
  • Posts

    4293
  • Joined

  • Last visited

Everything posted by Eldur

  1. Would be good to know the actual processor model, but I looked up the AMD which goes up to 4GHz. DCS likes high single core clock rates, and it's the most recent generation. Definately nothing wrong getting that one. And the 2060 mobile comes with 6GB of VRAM wheras I read the 1650 mobile is restricted to just 4GB which is pretty tight for DCS. I had lots of issues with my desktop 970 since the VRAM was already full on the absolutely lowest settings. I'm running DCS on an 8yo 3570k overclocked and a 1080 and I'm able to get decent 45fps with medium-highish settings in the Rift unless there's a ton of things happening at the same time. That AMD laptop should roughly be on par with that at least.
  2. By the definition of WVR, planes are within when they can be seen. And by that definition as well, in DCS the AIM-9 is a BVR missile for many ones. TL;DR of this thread, again: It's not realistic if it's not hard. In most cases you shouldn't be able to see more than just your HUD when looking forward, Yet people do fly all zoomed out 140° on totally unrealistic Ultrawides with a burqaesque FOV. BTW I discovered a long time ago that "specks" would be easier to see all zoomed out since all the detail around it is shrunken, but the contact is still being rendered as one pixel, even if it's just low contrast. Flying in realistic FOVs actually makes spotting harder, especially in VR where the resolution is a lot lower and therefor the single-pixel specks have even less contrast. Fun thing though about that discovery is that it apparently isn't like that from 2.5 on anymore, probably those were the "impostors" that's being talked about. I still was under that impression to have those until I got my Rift CV1 and suddenly wasn't able to see planes at around 1nm anymore, even in WWII. And I do have the same issue in that other sim where I always had the impression it was a lot easier to spot things in. Apparently, if things are too small for 1px, they just vanish. So you'd have to zoom on in to even be able to see things at all. But TBH, I at least don't use VR zoom to spot. It's there for ID things that have been spotted without already to overcome the low res. But usually it's just "tumbleweed, as always, blind, no joy" for me... Be wary of the fact that those guys who claim to see things at 30+nm and are crying to have the visibility decreased are running on 60+ inches 4k Pancakes or 1440p Ultrawides...
  3. The Su-24 mod will be great once done. I don't mind dropping the A-7, we'll be getting a full module A-7E from FlyingIron anyway.
  4. It's funny they reconsidered after the feedback on two _AFU_ updates that literally weren't tested at all except for the new map and 47 But I hope this prevents us from getting such catastrophes again
  5. When I still was flying pancake, I usually set my zoom/FOV to 60° and pulled it up to 30° for attacks and landings or to find targets around the general target area. Used 90° extremely rarely, I preferred to look down to see my dashboard. Now the point is that 30° actually was way closer to the real FOV than 60° and yet DCS even would have allowed me to zoom in up to 20° in most modules, I didn't need that though. Still was hard to find things. And now I see all the Tubers flying with settings like 140-160°, literally all the way zoomed out constantly and I'm really questioning on how they manage to see things there. Add to that that they don't use a wider, but actually vertically narrower screen mostly with ugly 21:9 aspect. DCS (and probably 99% of other games as well) FOV always sets around the horizonzal range, which means, you don't get more vision by having an ultrawide, but in fact you get less instead. And when I try to watch these, I'm literally looking at 1920x810 footage and I can't even read the effen dials there. Usually, I see the contacts first they've been calling out for minutes when they almost fill up the combiner glasses... I already had those "what are you even shootin' at?" moments there already... but well, this is also my eyes and the reason why I'm using dot labels. I just wish we had something better than that to help out. The scaling dropdown that was in the 2.0 Alphas for example was better and you couldn't see things though the dashboard and cockpit frames. Because of that issue I dropped the shaders mod and went to the migoto instead, sacrificing some vital frames to have it less gamey. After all I don't want to simulate being someone almost blind in a fighter that wouldn't even be allowed to sit behind a glider's controls. BTW since the OP is about ground targets, I don't have that much problems there, although I sometimes can't see s*** in certain lighting conditions withing the golden hours. If I know where to look at, I usually can find the things. Contacts in the air however is a completely different story. I can literally be flying in formation with my target at times without knowing his actual position... Now when it comes to spotting some airliners IRL that are up high and conning, it's much easier since we can hear those. And at least I can listen to them for a while and then turn my eyes to where I think it should be at that point considering the aural delay and usually it's spot on. But if someone's just pointing somewhere saying "Look right there", I'm completely blind In DCS, we can't hear other planes until we're really close to them, so this doesn't work here for a good reason. You couldn't either in RL.
  6. Where did I say something had a bad FM? Probably I wasn't clear enough. Initially I didn't buy the 101 because of my little interest in jet trainers and it being SFM. Then when I bought it, I did it for two reasons, to support the devs for their awesome work (as I've seen those tremendous fix lists for a while) and because of: So yes, I know it has an EFM for a while already, just didn't manage to dump time on that hairrdryer () yet. And if that "bad FM" thing was one of my previous statements somehwere else on the Gazelle, well - it's true. It has a bad FM with a horrible hardcoded deadzone in the cyclic that makes it feel as if you'd be controlling the thing with your cursor keys on the keyboard, or a digital Quickshot Pro plugged to an A500 which literally is just a giant 8-way trim hat with 2 buttons attached to it. But it's gonna be fixed after the KW arrived and I'm rather confident they'll be getting there after having seen some KW footage. Really looking forward to both actually. That aside, I am not a fan of SFM, which is why I'm really wishing for the A-4E-C to get that EFM eventually. Still, it's such a great mod that I do fly it every now and then even with SFM, which totally speaks for its overall quality
  7. I was under the impression that there is a dedicated server already that runs without graphics. Does it still have that non-working AI issue? As for the drop itself, you mentioned the reason: Tacview. Or somthing related to that. Disabling it nearly doubled my framerate with the latest versions that had them drop down to the drink.
  8. TL;DR of that is the rendered size at distance is correct. Problematic about this is that reflection glares and other optical phenomenons that would help are not modelled and on top of that, we don't have nearly as much contrast on a LCD screen as IRL. And then as a cherry on top of the icing, we don't have nearly as much dots per degree of angular resolution on our hardware to make it look real. Having to display the real angles on a low res usually results in a much less contrasted pixel (as in with more contrast it's easier to see as if it actually was bigger) which makes things harder to see than it might be IRL, in some other occasions it could be the other way round as well. It's hard to nail. Bottom line is: Someone sitting directly in front of a 65" 4K simply can't compare to someone running a CV1. That literally is apples and orang-utans. And as of now, it's known that spotting gets a lot easier with high rest hardware. In the past it was different. I remember back in Lomac as well as in that other sim people used to turn down their res simply because those 1px contacts would be bigger and therefor stand out more. I literally did that myself. I was able to run the other sim at 1600x1200 hooves down, but ran it at 1024x768 because of spotting. Others even turned it down to 800x600 or 640x480. As for Lomac... well, that didn't actually run at anything higher than 800x600 anyway without getting serious frametime issues.
  9. /me, totally unable to see contacts even on Youtube videos that are being called out, not even speaking of DCS itself without labels. Things literally are invisible if you don't know the exact location already. Digital Cloaking Simulator... This guy:
  10. I think this is the way to go anyway. With a decent weather sim that's planned it's absolutely mandatory, but I'd very much like to have that slider even before that.
  11. Hilarious. Too bad having the wings flipped up doesn't seem to change the drag...
  12. The throttle unit doesn't seem to bad for the price tag given there to get some extra axes. I don't like the pots of my Saitek quadrants... and when I bought these, I decided to get them because they had a lot wider movement range than the CH quadrant, which increases performance... well, not so much when the pots spike after a while.
  13. Would be great to have this updated since DCS added support for multiple audio devices a while ago, which rocks. All the comms, warnings and the walkman audio should come through the headphone device.
  14. Noticed something weird in my first 50979 run. FPS given by DCS were down again at 22 mostly, but it felt a lot better than that. Only in the end, after shutting down my Tomcat the counter actually rose up to 45. Guess it's time to grab fpsvr to get more reliable results
  15. Hi Rik, I'm probably late to the party, but I can't see a single server in BUNO 50979 with IPv6 disabled. Didn't try the last few ones though. Just enabled IPv6 because of this and now the list populates as expected.
  16. Pretty much this. I literally stopped flying SFM when the Su-25T dropped and luckily the original model got the FM as well. There were some rare occasions where I did hop into the other planes, but those were neglectable. And I never bought the Hawk because of this - when it finally got it's FM it still had so many issues... was similar for the 101. Bought it eventually with the Gazelle, both 50% off, but still I never tried it to date as opposed to the Gazelle. Yet still the A-4E-C amazes... but neverhteless I have two wishes that I won't get rid of until it happens: 1. The thing getting an EFM. 2. The thing becoming an actual module. I really hope that at least #1 will become true at some point...
  17. Found an Explorer extension tool and added a post on that to that thread.
  18. Found a tool that integrates into the Explorer context menu which does this, probably much easier for many: https://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html With that you'd basically just move the big folders somewhere else, and drag them back to the original folder with your right mouse button, then select Drop Here..., Junction.
  19. Today I opened my browser with the thought "ED probably just wanted to test us and have released an update today" and there it is I'm glad we did get a hotfix, thanks for that Missing out on a haze fog fix though, but the patch notes aren't complete if you haven't fired up DCS yourself after all That makes the HUD on the A/C that supposedly have been fixed already still unreadable if faced against the horizon It's always been harder to see in that state, but it's much worse at least in BUNO 50321 THRU 50793. I think it's a good way if they separate content updates from actual fixes in a way like they just did today with the hotfix. Having a content update every 4 weeks is totally OK for me, but if things got broken, I'd very much appreciate to see a fix after a week still. If they didn't bring fixes with a 4-6 weeks release cycle, the whole point of Open Beta would be superfluous and jasonbirder might be waiting for another 4-6 months until he gets his Stable fix which again might not be that stable after all TBH I absolutely wouldn't mind getting the old 2 week cycle back. Worked rather well until the ditched it around the Viper release. Taking the idea further I'd propose: Open Beta planned every 2 weeks Stable planned every 2 months with the actual goal of having it less bugged than the beta, which would mean it's not just a certain OB build taken over after a week. To get there: Last OB before planned Stable release is just for fixes, no content updates. So there's a whole month still that is just for fixing things so it can go to Stable in a decent state. Example: t - 6w: OB release with new features t - 5w: Hotfix release because something went south t - 4w: OB release with new features t - 2w: OB release that is just fixes t - 1.5w: Hotfix for something that got broken by another fix t - 1w: More intense closed beta test phase begins to make sure the upcoming Stable release exactly is that t: Stable release, jasonbirder happy t + 0.5w: If he wasn't happy, give him a hotfix to his Stable branch before adding new content for the next OB. Probably the most important point BTW I'm pretty sure those have been in there for ages, literally. Just depends on where you are, some places have them, others don't, but have other ambient sounds instead.
  20. Just FYI: I think those are called padeyes.
  21. I'm 120% sure it's definately not what we really need: Something that has FFB... and I'd love to be proven wrong
  22. Corrected that for you kthxbye. Oh wait... yes, all those books are terribly wrong! The Great Aero once said: "Where did you read about Spitfire made from a wood? Close this book forever and never open it again!" I can't even get to the M 2 given here since a few patches ago. Limit is just shy of 1.8 on a standard DCS day in Caucasus for a clean airframe just running out of fuel. But as the title sais, this is correct based on available charts
  23. Well, I'm officially poor TBH, and I still could afford all the modules, most of them on day one... Do you pay for the actual cup as well each time? I can have 16 cups for 2,99 (~24€ / kg), but I do have some "addon" costs for other ingredients like milk and sugar You weren't supposed to shoot up your chairs with that GAU-8... I'm still having the same one for the time being
  24. I want to have the HTS especially, even if it's just a dummy. It's impossible to trim the Viper out with just the teapot attached. It's either not enough or too much, guess the "counter pod" would help... Well, as opposed to other weapons, the Mav is reather basic... Guess we'll be stuck at toss/lofting 97s for a while - at least we do have these! And to be fair, an update planned for mid July easily can get delayed for two weeks™ if something funny shows up within the last few days before a planned release... I mean, they have to fix it - and also test it again. If they don't test it thoroughly then and the fix has broken some other things again, torches and pitchforks will be Legion because "why release a broken patch after 7 weeks when we can have a broken patch in 1-2 weeks instead?" I'm rather confident the longer patch cycles won't solve the patch quality issues at all... but we'd have to live a lot longer with issues that could be fixed rather shortly.
×
×
  • Create New...