Jump to content

danpaul88

Admins
  • Posts

    3,639
  • Joined

  • Last visited

  • Days Won

    85
  • Donations

    225.00 USD 

Posts posted by danpaul88

  1. The launcher queries Windows for all the supported resolutions for your monitor and lets you pick from those - it's not got a built in list. So if whatever size you want isn't listed that's because Windows doesn't think your monitors support that size

  2. On 8/15/2018 at 2:53 PM, OrangeP47 said:

    I don't buy many new releases, but I just want to say I enjoy seeing Two-Point Hospital get some love.  I really liked the original dos game.

    I still go back and play the original theme hospital now and then. EA gave it away for free on origin a few years ago with a dosbox wrapper. I can't think of any other game I've gone back to over and over again over such a long period...

  3. I think we should look at ways to integrate this with / into the launcher going forwards so people don't need half a dozen things installed. Will look into it when I'm home in a few weeks, amongst other things.

    If this is written in c# we could possibly reuse bits of it ?

  4. Thanks for uploading that @ganein14 . Is that definitely the 'broken' copy of the file though, from before you fixed it? Reason I ask is that a binary compare against a known 'good' copy shows it is identical to the original, which suggests it downloaded successfully, thus should have installed correctly...

    If that is the 'broken' file then it suggests the problem isn't a corrupted file (which explain why the launcher doesn't delete it and redownload it), so that blows my original theory out the water...

  5. I'd love to get my hands on a copy of that 'broken' always2 so I can find out why it breaks...
     

    As for Linux, the launcher uses .net 4.6 and wpf. Typically it's the wpf bit that falls over on Linux because it's not been ported to wine. I am starting to move some of the underlying libraries over to net standard (which does support Linux) which might give us the option in future of a command line Linux client (I don't see much prospect of porting the GUI any time soon) but there's just not much demand for Linux support in the community so it's very much on the back burner right now.

     

    I know Omar got the launcher working on Linux at one point and even contributed a few code tweaks to help improve the support but I'm not sure if he's around at the moment

     

  6. Hadn't thought of that, although it could be argued holding onto the flare for that long is less useful than a failed attempt which then allows a new flare to spawn - plus if you're lurking as a spy doing nothing for 15 minutes waiting for the perfect opportunity to plant a flare your team is effectively a player down in the field for a long time. Just my 2 cents, it's a long time since I've played so maybe I'm just out of touch.

  7. Random thought - flares have a time limit to be used, if you hold onto it for too long (6,7 minutes? That's enough time to rush and die or plant) it just disappears from your inventory and a new one will spawn.


    Won't stop people literally sitting on top of the spawn point the whole game but they're easy to report to a mod that way because it's obvious who is stood there waiting

  8. I'm not sure why the APB team are still using msvc 2013 in the first place, I thought it wasn't needed anymore... Might need to check up on that.


    In the meantime, the error you're seeing is that Microsoft's visual c runtime (msvc) isn't installing correctly - we just run the installer that Microsoft provide so I'm not sure why that would fail. Can you send me the errors.txt file from my documents/w3d hub/launcher so we can see what the Microsoft installer reported as an error (if anything)

  9. Vsync means a frame won't be rendered until the monitor is ready to display it, which means that if the monitor refreshes every 10ms and it takes 11ms to render a new frame then you'll only see a new frame on screen every 20ms. If you're seeing 30 FPS then your system is probably not quite capable of hitting 60 fps so it ends up halving the frame rate since each new frame is slightly too late for the next refresh and then waits for the refresh after that one

    In practice you'll see exactly what you'd see with vsync disabled but it'll avoid rendering more often than it can sync with the monitor.

×
×
  • Create New...