• Content count

  • Joined

  • Last visited

About Edward850

  • Rank
    Senior Member
  1. I reread your question; Both controllers are controlling player 1 because you need to reconfigure which controllers are bound to which player. You'll find this above the profile configs that you found. Remember, the keyboard always controls player 1, and cannot be configured to a different player.
  2. Are you talking about the splitscreen branch? It's better to direct splitscreen question in there, it has nothing to do with Eternity in general at the moment. And at the moment you cannot, there is only one available set of bindings for all controllers connected.
  3. Set MN_CLASSIC_MENUS to 0, you can set this in the console.
  4. If it didn't have frame "skipping", its multiplayer wouldn't work at all. All Doom PC ports will process multiple gametics in a single cycle based on the amount of input collected since the last frame. This is derived from the networking logic that maintains/controls input creation and processing from the local and remote nodes, where the gametic processor waits until all inputs are received for a single frame, and will process multiple gametics to catch-up if enough inputs exist (for either performance or networking reasons). This behavior is directly derived from vanilla. ZDoom keeps the same behavior, although actually has a bigger local input buffer so it can construct more player commands, resulting in more gametics processed between rendering if things slow down.
  5. You have vastly more important problems to focus on than not being able to import a image into a Doom WAD, namely sorting your potentially failing graphics card or other hardware.
  6. The Red Cross symbol is not copyrighted, it's protected under international treaty and isn't actually public domain.
  7. Backgourd
  8. Incorrect. The fix only affects tasks switching between kernel and user space memory. Doom source ports don't exactly do this often, and Doom itself has very little I/O. The only types of systems that'll be largely affected is VM server farms and I/O heavy processing such has databases.
  9. Short answer, no. Long answer nooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo...
  10. It's not old vs new, computers don't work like that. In this case, it's tiers. New hardware has more capabilities, but performance is an aspect of the tier you bought it. Consider the difference between two graphics cards, a GTX 670 and a GT 1030; the 1030 may be newer and thus supports more things like DirectX12, but the GTX670 will continue to run rings around it because of its raw horsepower (the 1030 being some of the shelf $80 card and the GTX670 costing you around $500). If you wanted to buy something newer and better, it would have to be something like a GTX1070, which is the same hardware tier and thus will have both more features, but also be faster without a doubt because it's the same hardware tier as the 670 but with newer chipset manufacturing techniques. If you want a better way to view it, always look at the original market values of both units, cost usually says it all. (Plus APUs simply aren't fit for that purpose anyway so it was a non-starter this whole time; it simply wasn't built for that job)
  11. That's a fairly weak APU with no actual independent VRAM (and what it has allocated is little at that). Coupled with the fairly low end 1.5 GHz CPU, you likely have your culprit right there. Put simply that chip wasn't meant for games, but rather basic media like videos and web browsing. Not to say you couldn't push on; With the low clock speed, I'd try lowering the screen resolution in addition to the other game settings, as that should reduce the fillrate.
  12. Again, can you tell us what the GPU is?
  13. You grossly overestimate the GPU processing power in lower end laptops and chipsets, especially ones designed for battery efficiency.
  14. Why wouldn't it? Doom3 needs the GPU to render the scene, does it not?
  15. Doom3 works demonstrably fine on Windows 10, and nothing you said made rational sense. @MancubusBruiser1988's issue is likely driver related instead, or because it's a laptop, power related. Check that all graphics drivers are installed and up-to-date, and make sure the laptop has no power saving modes enabled on any of its provided software (at 1.5GHz you really don't have much leg room in any sort of power saving mode). Also you need to list your GPU, or GPUs as most nowadays sometimes have two for two different power modes, this is especially important as Doom3 predates that tech and wont be auto-configuring to your best available GPU on a laptop.