Need For Speed Shift Pcgamingwiki
Magdalen Dano
Hello,
I have bought need for speed 2015 yesterday and have been playing it with the controller (Dualshock 4) and had no problems until today. Whenever I try to drive with controller car acts weird (will not accelerate to its full potential, won't go back or in case of dodge viper it does burnouts in reverse). I tried re-calibrating my controller, reinstalling my drivers, tried it on other games and it had no problems either (BF4) and even tried to rebind acceleration to X on my controller (to make sure that it wont accidentally press) yet problem did not disappear. My controller is new I bought it two days ago and I am sure it is need for speed's fault, I would greatly appreciate if you can help me to fix this problem.
Thank you.
I just bought a new NFS deluxe edition and play for a few hours, then I have encountered that my car couldn't accelerate properly it reached 3rd gear and can't go faster or gear up to 4th gear, also when I just pressed accelerate my car keeps bending a little bit right even if I didn't try to go right. When I tried to move backward my car stops moving (I used Xbox controller connect to laptop via bluetooth). I look for car repairing at the fuel station and found spanner symbol it kind of did something but the problems still there. It's very frustrating please help.
I noticed that before issue I can see the button in game showing the same with Xbox controller but after issue happened the button in the game still showing like keyboard button even though I'm using Xbox controller.
@cooletsexyAfter spending the whole night searching for a solution, finally i've found one.... Windows detects the xbox one s controller as a Xinput device. Keyboard an steering wheel are directinput devices. In order to prevent NFS to mix up the controls, you have to "block" all direct input devices. The dinput8.dll in the Solution will block all direct input devices.
The latest release seems to have completely broken my build. I'm running VirtualBox 6.0.24 and the previous release (the 7/10 release) seemed to do nicely for most things I was running. The GLChecker worked great, showing I had HW acceleration as did dxdiag, showing blazingly fast D3D support.
The first (albeit minor) issue is that the mouse cursor has, for some reason, become extremely tiny. I tried running GLChecker and it simply froze everything, never launching. I ran dxdiag, and it starts to load but then eventually just stops loading. I can't get any further with either.
Update: I tried running the newest driver package on the newest VirtualBox (7.0.10) and while the testing does work in this version (GLChecker and dxdiag are fine), the mouse issue persists. Not only is the mouse cursor extremely small, but when I try to play something like Unreal Gold, the mouse is only available for the top quarter of the screen, and once I move the cursor down, it completely disappears. Clearly there's some kind of bug that completely breaks earlier versions of VirtualBox and wrecks mouse functionality of the newest version.
After installing the new SoftGPU driver, Windows 98 installed in VMWare Workstation Player 16.2.5 now flatly refuses to boot and writes "EMM386 Unrecoverable privileged operation error #01".
If I select B, the virtual machine will still not start, and if I select C, it will crash to the host's desktop.
Disabling CD, Floppy, network adapter, sound card, 3D acceleration and enabling Intel VT-X/EPT and AMD-V/RVI do not help.
What to do?
upd: Thanks to all! Unfortunately, I had to re-create the virtual machine and install Windows 98 into it, but during installation I did not check the "Enable SSE/AVX hack" checkbox. As it turned out, it is because of this option that Windows 98 does not boot for me.
I would suggest trying VirtualBox 7 as it seems SoftGPU is currently more taliored to it, rather than VirtualBox 6 or VMware.
As for mouse issues, is the pointing device set to PS/2 Mouse? To smoothen the mouse you can try PS2Rate utility.
Or select your real USB Mouse from USB menu.
I would love to, but in VirtualBox, in addition to Windows 98, I also have Windows XP (and there, starting from version 6.1, there is no support for 3D acceleration). In addition, some games work best in the same Windows XP that is installed in VirtualBox (for example, in the game Mickey Saves the Day on VMWare Player 16.2.5 there are no characters at all, and in The Simpsons Hit and Run Homer's car dyed black instead of pink).
When SoftGPU will take over the development of the driver for XP is unknown. Using a real computer is not an option.
Why is that? Mickey seems to be running just fine on Windows 10, and if some issues do pop up at some point, you can use dgvoodoo2. Besides, it's a Windows 9x compatible Direct3D 7 game, so I don't see why you insist on running it on XP.
For Simpsons, again, a wrapper like dgvoodoo2 or d3d8to9 on modern windows can do the job, and if that's not enough, there's a community made launcher that not only wraps it to D3D9 but also fixes bugs, adds modern aspect ratios, resolutions, MSAA, etc.
It's just that I'm afraid to accidentally install old libraries (suddenly the installer won't allow it) designed for old Windows, and thereby ruin my Windows 10. That's why I prefer to "experiment" in virtual machines. And, as for me, it's better to run games on "native" operating systems. I'm not considering buying an old PC yet. Does anyone else know how to fix this issue?
I don't know if it's just me but from what I've noticed after using softgpu on both vbox and vmware are several things:
1. VMware is snappier compared to virtualbox, animations are instantaneous almost.
2. Enabling 3D acceleration on tasks before the driver is initialized (install, dos mode, second stage) on vmware makes them almost unusable.
3. VMware hates VxD drivers for the SB128 as most drivers BSOD the VM during the install. Eax seems to work with half-life at least, but under the WDM drivers, the latency is so bad.
4. VBox seems to be more stable than VMware. Recently, after updating the drivers, there are times where vmware would lock up and refuse to boot resulting in a black screen.
5. Under VMware, openGL seems to perform better as serious sam on normal settings performs better. But on VBox, D3D seems to perform better under the VMSVGA device. Serious sam performs worse at the same settings regardless of resolution. Unreal works fine on VMware under D3D, while on VBox, I need to use nGlide in order to play it.
6. Dualshock 4 passthrough works fine under VBox, while VMware doesn't work for some reason. Even with nUSB.
Only for a few games. Thus far I've done an informal (i.e. not with exact benchmarking) test of Unreal, Unreal Tournament, Rogue Squadron 3D, and Need for Speed 3. My PC host is an intel i7 11800H running Windows 11 with 64 GB of RAM and a 6GB NVIDIA RTX 3060.
The thing to know about PCem vs VirtualBox is that they seemingly have the exact opposite bottlenecks: VirtualBox's virtualized CPU is blazingly fast, but SoftGPU under OpenGL, DirectX, and/or OpenGlide wrapper all render the graphics seemingly slower than the virtual Voodoo GPUs of PCem, at least they seemed a lot choppier for me. Meanwhile, PCem has a massive CPU bottleneck, where the rendering seems to do well, but only being able to run a maximum 200MHz CPU with my machine is what slows everything down. This was evident especially in running the Uneal games, as they ran slightly better on PCem. Rogue Squadron was a different story where on VirtualBox the game ran ridiculously fast, where I'd have to throttle the virtualized CPU somehow to get it to run at a playably slow speed, whereas PCem had the opposite problem of running the game a bit too slowly. Need for Speed 3 ran better in VirtualBox + softgpu, with one caveat: I had to turn off Z-buffering, because it made everything a pale shade of white. Other than that, it ran faster and the rendering was just as good as PCem.
I feel like the perfect emulation solution that, to my knowledge does not yet exist for emulating Windows 95-Windows ME games (basically the 3dfx era in general) would be something that does HLE for the CPU, something closer to VirtualBox's virtualization than what low-level PCem/86Box does and does LLE of the GPU, something closer to how PCem/86Box handles and recognizes Voodoo cards as opposed to the seemingly hacky nature of SoftGPU. It's also a bit trickier to setup softGPU, having to make sure you have the right dlls in the game folder, often having to hack the registry of a game to trick it into thinking you have a voodoo card when you're using an OpenGlide wrapper (as was the case with NFS 3). Thus far, I haven't found anything close to that, but if SoftGPU continues in the right direction and works out the bugs, I'm hopeful it'll still be better than PCem/86Box, it's just not there yet.
93ddb68554