Duke4.net Forums: Bugs & Problems - Duke4.net Forums

Jump to content

  • 37 Pages +
  • « First
  • 35
  • 36
  • 37
  • You cannot start a new topic
  • You cannot reply to this topic

Bugs & Problems

#1081

DukeGDX: With 20th Anniversary World Tour and "Legacy Duke Talk" on, the voice clip at Hollywood Holocaust (E1M1) still plays the re-recorded line from the 20th Anniversary World Tour Edition rather than the original voice clip.
0

User is offline   m210« 

#1082

 Szczwanylisek, on 01 June 2020 - 05:06 AM, said:

That my, with Win xp too :) ?

Not yet
0

#1083

No worry, i know im in that 1% od people usage win xp for retro gaming. 🙂
0

User is offline   Kil3r 

#1084

I'm someone who is fairly anal about mouse aim quality in games and I believe you did a good job. It feels responsive and is certainly playable. However, I noticed that there is a problem. When you move the mouse very fast, the mouse input does not register. For example, when you try to quickly turn around and shoot something behind you.

Two ways to reproduce this issue:
1. Move the mouse very fast in one direction. For example, try to do a 180 degree turn very fast.
2. Move the mouse very fast left and right repeatedly.

The result will be much slower camera movement than expected. It could even result in almost no camera movement after your mouse hits a certain speed. This is known by mouse look complainers(such as myself) as negative mouse acceleration. For comparison sake, you can try the same thing on games such as CSGO or even EDuke32.

Games: BloodGDX and WangGDX (likely occurs on any BuildGDX game)
Windows 10
Logitech G Pro Wireless Gaming Mouse

This post has been edited by Kil3r: 10 June 2020 - 03:08 PM

0

User is offline   t800 

#1085

So, after long time I decided to try latest version of BuildGDX. And no matter which game I run in it, I just cant get to run Classic renderer properly in fullscreen. I get black screen with only sound running. Windowed mode works fine with it, but then I get ridiculously low framerate, going around 20-15 fps. Where is problem? Polymost works alright for me. BTW I tried version with packed JRE and also without it and still no difference.

My laptop specs:
OS: Windows 7 64 bit SP1
CPU: AMD A-8-7410
GPU: Radeon R5 M330
RAM: 8GB

Hopefully, I wont get reply like "Get stronger computer" :D

This post has been edited by t800: 12 June 2020 - 04:39 AM

0

#1086

I have the same issues on my retro pc with win xp, but screen is white. Its something with Java
0

#1087

WangGDX: There's a triangle on the lower right corner of the screen that keeps trailing on-screen sprites/weapon bobbin' at some points, just like when activating noclip cheat and going out of the map.
All GDX games: A tall thin line fickers at some points.
Using Polymost rendering. Haven't tried software mode.
0

User is offline   gordon81 

#1088

Hello, after BuildGDX v1.12 (13.06.2020) uptade, the powerslave/exhumed wont launch. ┐can i download previus release 1.11?.

"there was a problem initialising the build engine: Couldn┤t read file null".
0

User is offline   Tekedon 

#1089

Love the new release! But the HUD seems a little tiny bit stretched. Or it might just be me.
0

User is offline   Jim 

#1090

The hud is indeed streched. And the last warrior crashes after the intro plays. It seems there is a problem of loading maps after intro plays

This post has been edited by Jim: 24 June 2020 - 05:13 PM

0

User is offline   fgsfds 

#1091

SW crash was fixed, download 1.13 again.
0

User is offline   Tekedon 

#1092

In 1.13 you can't change weapons with mousewheel while holding the voodoo-doll and running. Works if you use "vanilla mode". So probably something to do with the fixed voodoo animation.
0

User is offline   Gagert 

#1093

How do I make the included demos run in the main menu of Blood while using BuildGDX? They are currently named blood000.dem, blood001.dem, blood002.dem and blood003.dem and is within the BuildGDX folder a made for Blood (I made a copy of BuildGDX for each build-engine game). I tried renaming the *.dem files to demo001 and so on, but whatever I do the console says there's 0 demos in loop.
0

User is offline   m210« 

#1094

 Gagert, on 26 June 2020 - 05:22 AM, said:

How do I make the included demos run in the main menu of Blood while using BuildGDX? They are currently named blood000.dem, blood001.dem, blood002.dem and blood003.dem and is within the BuildGDX folder a made for Blood (I made a copy of BuildGDX for each build-engine game). I tried renaming the *.dem files to demo001 and so on, but whatever I do the console says there's 0 demos in loop.

Be sure, that you're using dem files from version 1.21. The version should be "277"

This post has been edited by m210«: 28 June 2020 - 09:58 PM

0

Share this topic:


  • 37 Pages +
  • « First
  • 35
  • 36
  • 37
  • You cannot start a new topic
  • You cannot reply to this topic


All copyrights and trademarks not owned by Voidpoint, LLC are the sole property of their respective owners. Play Ion Fury! ;) © Voidpoint, LLC

Enter your sign in name and password


Sign in options