Paraso
-
Posts
15 -
Joined
-
Last visited
1 Follower
-
week_away.mp4
-
Cutting ties is exactly what will happen if the ridiculous dispute cannot be solved. However, in the meantime, I think it is uncontroversial to assume there is almost nobody on Earth who would prefer that to occur over a resumption of updates to existing titles.
-
So purge means resolution soon? Sick
-
This, but instead of "My best friend's sister's boyfriend's brother's girlfriend heard from this guy who knows this kid who's going with the girl who saw Ferris pass out at 31 flavors last night" try "Ferris told me they passed out at 31 flavors last night". Doesn't make it true, but I don't think any of us are maniacs for bringing it up. (In fact I hope it's not true because if it is, it paints ED in a disgusting light)
-
Yes, be very careful about sources you listen to on the internet, on all sides
-
Paraso changed their profile photo -
Sentiment from RB staff suggests any disagreement/dispute which initially led to this mess has been solved/finalized/settled for some months, and the ball no longer rests in RB's court to bring it to a close. Such are not official statements and thus unactionable by us as a community. It seems just about everyone on the planet aware of the dispute would like it resolved, which makes it curious as to why it has not already been, assuming we take the claim of the supposed IP dispute already having been crushed as truth. Not an accusation against ED, just interpretation. As @Mike Force Team says, patience is key.
-
There was talk of 'dangling a settlement' and a 'no intention to pay RB' in April by a certain SME exactly one day after the modules were taken down from the store, so mention of the word but no mention of a signing. One month earlier (in March) Razbam CEO stated he'd regained access to his developer account and was optimistic about a positive resolution, yet a month later their modules were removed from sale. It seems a story worth considering that supposedly a settlement may have been finalized sometime in or around March, and then payment has not come through for one reason or another. Speculation.
-
Agreed - outside of speculating any contractual obligations, and judging by the most recent post on their discord, they seem pretty adamant that they have not a speck of interest in voluntarily giving up any source code at any point. Current intentions aren't exactly clear but there's sentiment floating around that they aim to deal with this mess as quickly as possible (and get the show back on the road?), or so we would hope. Only time will tell
-
Regardless of the outcome of the legal dispute, I'd like to take the moment to vocalize my support for ED or RB or (insert 3rd party dev here) to keep the F-15E alive.
-
At this point I've got my fingers crossed hoping for a friendly billionaire to come along and subsidize resolution & further development, all out of pocket Unbelievable.
-
Hi, how did you manage to confirm your GPU was overclocked from factory? Using GPU-Z my "GPU Clock" and "Default Clock" are the same value. Haven't checked MSI Afterburner yet. I have the "THICC III Ultra" 5700XT. EDIT: Found that my GPU's P3 clock was set to 2084 mhz when the manufacturer defined stock boost clock setting was 2025 mhz. I set p3 to 2025 mhz using Radeon adrenalin software and attempted to run MT, CTD after a couple of minutes - log below. Manufacturer also lists base clock as 1810mhz and game clock as 1935mhz, not sure if I should be setting P3 clock to either of those, or what even counts as an OC in this case. dcs.log-20230701-034601.zip
-
Thanks, I'll try the ones that apply to me and report back. I am using a 5700XT, I'll still try out some of the fixes but that really is a bummer.
-
I've looked through countless threads regarding this issue and all of the solutions I've tried so far either don't apply to me or haven't worked. I'm experiencing a DXGI device removed crash on OB MT within 20 minutes of spawning into a mission. I have never experienced this error/crash in non-MT OB nor any consistent GPU-based error/crash in any other game I've played. Log from today (6/24) was using the ryzen high performance power plan, featuring only one DXGI error near the bottom. Log from (6/09) was using the ryzen balanced performance plan, with many DXGI errors. Neither setting "TdrLevel" to 0 nor setting any delay in registry editor have ever given positive results, however for the 6/24 log neither of those settings were actually in place. I don't have any overclocking or volting changes, I've yet to try any of the default windows power plans, setting a custom pagefile also has not yielded any positive results though again that was not set in the case of the 6/24 log. Custom RAM profile is enabled in the BIOS though my RAM is on the slower side (2400mhz). I don't have Volanta's plugin for DCS nor aorus engine. dcs.log-20230609-034157.zip dcs.log-20230624-215259.zip
-
Any chance you could add Titanic?
