Bias FX 2 Crashing to Desktop
-
I have updated Bias FX 2 with the March 8th update and now Bias Fx 2 crashes every time I try to add an effect to the FX chain.
Anyone else experiencing this?Any help would be great!
-
I noticed the very same issue.
I am on a Apple iMac and when the app does not crash it is very slow compared to before the upgrade. Response changing from amp panel to patch list for example. -
I have the same issue. just bought the riff with bias fx 2 pro. I am on a pc windows 10
-
same, what's going on here. highly annoying, breaks the entire software.
no fix in weeks? -
Same here using Windows 10. I'd say that 80% of the time I try to add an effect to a signal chain BIAS FX 2 crashes to desktop. Diagnostics from the Reliability Monitors show:
Problem Event Name: APPCRASH
Application Name: BIAS FX 2_x64.exe
Application Version: 2.4.4.6350This is a SERIOUS bug! Please fix ASAP.
-
This post is deleted! -
Yep, same for me, it's doing me head in a little. Have a simple chain and just adding a noise gate is enough to send me crashing to the desktop.
For other effects I found I could add with a double click, THEN move the fx unit into the signal chain where I wanted OK, but drag and dropping to where I wanted it would crash the program. For the noise gate, it doesn't matter how I do it.
Very irritating.
I'm on Windows 10 as well fwiw.
-
same issue on my end
Ran compatibility mode all the way down to Vista, no luck. Not a windows version issue.
Swapped some settings in properties, so far getting some results - tested dropping / adding/swapping amps plugins pedals, etc no crash
What I did to get some better results (so far, only tested today for a few hours)
(Default install location: C:\Program Files\BIAS FX 2 Application (64bit)\BIAS FX 2_x64.exe)Settings:
Right click on the bias fx .exe > Properties > CompatibilityCheck:
- Disable Fullscreen Optimizations
- Run as admin
- Use legacy display ICC color management
I am assuming this problem must be similar to hardware/software specific after scrolling for hours through Reddit and watching the event log in windows
Are we all on AMD graphics by chance?
Please respond with any similar hardware components, that might help us isolate the issue.
I put in a support request already, waiting on a response.
i7-8700K
AMD 6700XT (Adrenaline Driver)
PreSonus Studio26c USB (Universal Control Drivers / Everything installed)
Corsair mouse / keyboard / ram - running iCue
Arturia MK2 Minilab
GSP1101 (USB)
ASUS MoboModerate overclock/water loop, @ 5.1 - the system is stable even under full gaming/video editing load, so it's not because of overclocking, the app crashed at intel defaults, and bios defaults as well under the same conditions.
Also plugged in via USB:
Astro Mixamp
Multiple WebcamsI'll mention my DAW just for kicks because the software in standalone mode crashed as well, so I doubt the DAW matters.
Studio One 5/Sphere -
@hxhippy Crashed again after heavy use for a while.
Still must be resolved, please advise
-
Updated, the response from Positive Grid:
-
@ivity-creat what Imac do You have? I have a 2015late version of 27", with 16g Ram, and facing the same lagging and crash. I was thinking that I would need to upgrade the Mac, but would be nice if You can confirm which version of Imac is normally working fine with FX2.
Is the downgrade patch helped You?Thanks!
-
@hxhippy did it work to you? they gave me two different previous Versions but it still not working.
-
same issue for me on windows 10
-
Does the software requires internet connection ?
It seems that the crashes happens consistently if the computer is not connected to the internet. I can reproduce it consistently. -
@eph Today I bought Bias FX2 Pro.
Same issue.
MBP M1 Big Sur 11.6.4 -
@joan-paz Currently with the version they gave me (see link above for version) it is working as intended. Using ASIO driver, no issues.
Working as standalone and within DAW via VST3.
Based on how many people this solution did not help out, it's safe to assume that internal PC hardware and drivers play a significant role in this glitch. They likely didn't add support for common drivers or system configurations.
Running:
Presonus 26c, factory drivers via Universal Control
ASIO4All driver to decrease latency
Intel i7 8700K @ 5.1
64GB 3200 DDR4 Corsair Pro Ram / 4 sticks, set XMP/Dual Channel
Windows 11 dev build
Studio One 5/SphereUnused with bias, but running concurrently:
GSP1101, c63 firmware xedit Via USB/MIDI
Arturia MKII MIDI/USB
GTX1080 / factory clock speedsMaybe rerouting driver through ASIO4All is part of the solution?
-
@rex-progrock I get the frustration, I dug around on YouTube looking for a digital option for amp sims that aren't trash, this or native instruments were the clear frontrunners. I opted for this software because of the amount of effects and configurations I could build, and I've been pleased with the results... When the software works.
I bought the top tier pack with the metal add on, big investment, I expected it to work immediately and flawlessly. It did not. I had to find the right drivers, the right frequency settings, and roll back to the older version for the software to be compatible.
Their QA team needs to test more environments, and have a better error data collection policy to ensure they are being proactive in developing the software to the fullest extent.
Be aware though, drivers, bitrate, additional installed components etc greatly increase the chance of driver compatibility issues. Try all the configs you can before giving up entirely.
It's possible their team has enough data to point you in the right direction if you give them even seemingly unnecessary driver / concurrently running software while using the bias software, it can have a significant impact. If it doesn't work after all that, I'd get in touch with them for a refund. No idea if they would honor it, but it'd be worth the discussion.
I've been a developer for over 17 years now, and a musician for longer than that, so I've dealt with it all, good, bad, indifferent. This company is at least responsive to support tickets, which is a plus. It's not a good situation overall and in no way should be normalized, but it's what we've got unless you buy other software. Fortunately, they got the software running on my build with the system specs stated above.
-
It seems that the crashes happens consistently if the computer is not connected to the internet. I can reproduce it consistently.
-
I just downloaded BiasFx2, it is unusable, it doesn't appear to be compatible with Reaper Daw at all every time I load an instance it crashes Reaper, the stand alone cashes when selecting single or dual chain. Tried solutions from other threads as well as support, for one there is no folder named Bias in documents, just Bias_pedals and another named Positive Grid and thats it, so far this plugin is unusable. I'm on Windows 10 version 22H2, with Roland Quad capture and running latest version of Reaper.