Jump to content

sobek

Members
  • Posts

    12402
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by sobek

  1. 6 hours ago, St4rgun said:

    "You have no idea what you are talking about." Sorry, what?

    You heard me. If the physics engine ran at anything close to as low as what the graphics engine runs, the input lag alone would be horrible.

     

      

    6 hours ago, St4rgun said:

    Everything else in the simulation can wait. The graphics cant.

    Again, you do not understand the consequences of what you propose here. This would break the simulation.

  2. On 11/14/2022 at 11:54 AM, St4rgun said:

    Who cares if the flight model is updated "only" 20 times a second? Or if the calculation of a missile control system updated only 10 per seconds? Or all the instruments in the cockpit at lower interval? Personally I don't care if the sound of an impact is late by 0,1 s (of course the interaction sounds should be prompt).

    You have no idea what you are talking about. If you don't enforce a frame rate for the physics rendering, the differing quantisation errors add up over time and lead to completely different results. The graphics rendering doesn't necessarily need to run on a fixed fraction of that, but the physics engine very much needs to have a constant frame rate, otherwise it will start behaving very wonky.

  3. On 10/9/2022 at 7:35 PM, Dragon1-1 said:

    DCS is new enough to be somewhat modular, though, which means you don't have to touch legacy code - you can chuck it outright, but only if you have a replacement handy. This is what ED is doing now, there's absolutely zero DX12 code that can be transferred to Vulkan, it's a whole other paradigm. This is also why you see systems replaced the way they are, it's not worth trying to fix the old AI, old ATC and so on. Rather, they're replacing those systems with completely new ones.

    Making a new engine from scratch would be more or less the same thing, TBH, only it couldn't be done in stages. 

    The graphics and physics rendering is monolithic and has been since the days of LockOn.

  4. Dunno, general public MP servers don't do it for me. It's all individuals flying around as lone wolfs, where I'd rather fly cooperatively as part of a bigger package. But the logistics of that are so complicated and time consuming that it never works out. In time I'm sure the AI will suck less and the campaign dudes will churn out some content. I've got enough stuff to do to tide me over. 😉

    • Like 1
  5. 1 hour ago, 159th_Viper said:

    long time no speak

    Ain' t that the truth.

    Interesting times to say the least, but all things considered, I'm doing very well. How are you doing? Btw. why ain't you on Mudspike? That's where I hang around these days...

  6. On 8/1/2021 at 11:05 AM, Bricux said:

    Since "our" F-16 is describled as CM blk. 50 version, its means the same like C 50+ (C 50 Plus)? If it's, that means we should get V(9) with SAR. 

     

    "The first production V(9) radar, which was delivered in April 2002". DCS F-16 is around 2007, so we should (i hope) get (V)9 radar 🙂 

     

     

    Last I checked it was specifically stated that we do NOT get the (V)9 but the (V)5. Personally I'd love a (V)9, but I wouldn't get my hopes up.

  7. It shoudl be obvious by now

     

    It isn't, because it keeps changing, without notice. I've been following ED very closely since before the first BlackShark was released, i've been a translator and moderator with more insight into how they work than the average customer for quite a few years. I understand the hardships that cause these issues, since I've been a developer myself for well over 6 years now. Even putting all this into the mix, ED still manage to throw me the the occasional curve ball, to the point where i find it hard to still be excited about development and the product itself.

×
×
  • Create New...