DGDecNV build 238 will not run but 236/237 do
DGDecNV build 238 will not run but 236/237 do
I am getting an error with the latest build of DGdecNV 238, it will not run and shows an error window as you can see below. I am using Windows 7 x64 SP1 with an Intel i7-3770K CPU and a MSI GTX 1660 GPU. v236 and v237 both run without problems. It's the same for both the x86 and x64 versions.
DGDecNV build 238 will not run but 236/237 do
Might be a win7 thing.
Just tested x64 and x86 on win10 and it works fine
Just tested x64 and x86 on win10 and it works fine
DGDecNV build 238 will not run but 236/237 do
DPI awareness
DGDecNV build 238 will not run but 236/237 do
I'll look into supporting Win 7 tomorrow.
DGDecNV build 238 will not run but 236/237 do
Thanks, there is no rush, it's a busy time of year for many. It is good to know it is on the to do list.
Maybe there is a way to check for the OS and not offer DPI awareness if it is not supported? Presumably this is for 4K displays? I am not aware of the maximum display support in Win 7 because my monitor is only FullHD. DPI awareness might be more than that though.
I did try Win 10 but could not stand it. It was unusable. It's like a lot of software these days, people seem to think that giant buttons are a great idea when they take a large amount of display space and only look like a child's toy. lol
As you can see from my window colour, I dislike white backgrounds which is hard to get rid of fully in Win 10. The dark feature does not get rid of all of it. Themes never really worked well for me on Win 7. Dark themes are difficult to use.
Maybe there is a way to check for the OS and not offer DPI awareness if it is not supported? Presumably this is for 4K displays? I am not aware of the maximum display support in Win 7 because my monitor is only FullHD. DPI awareness might be more than that though.
I did try Win 10 but could not stand it. It was unusable. It's like a lot of software these days, people seem to think that giant buttons are a great idea when they take a large amount of display space and only look like a child's toy. lol
As you can see from my window colour, I dislike white backgrounds which is hard to get rid of fully in Win 10. The dark feature does not get rid of all of it. Themes never really worked well for me on Win 7. Dark themes are difficult to use.
DGDecNV build 238 will not run but 236/237 do
Yes that runs and seems to work like 237 apart from the buttons being at the top and the button bar being white.
DGDecNV build 238 will not run but 236/237 do
That's great news. Glad you like it. Thank you for your testing, RedDwarf. I'll update the release.
Now somebody is going to say what about XP?
We call that "overall cleaner look".buttons being at the top and the button bar being white
Now somebody is going to say what about XP?
DGDecNV build 238 will not run but 236/237 do
Not so fast, Rocky!
DGDecNV build 238 will not run but 236/237 do
Beautiful. Sung from the heart.
DGDecNV build 238 will not run but 236/237 do
"No matter how they toss the dice, it had to be."
Profound understanding there.
Profound understanding there.
DGDecNV build 238 will not run but 236/237 do
Say thank you.
- Bullwinkle
- Posts: 344
- Joined: Thu Sep 05, 2019 6:37 pm
DGDecNV build 238 will not run but 236/237 do
And for the more cerebral mammals such as the glorious Moose:
- Mr. Peabody
- Posts: 46
- Joined: Tue Dec 24, 2019 9:20 am
DGDecNV build 238 will not run but 236/237 do
Ah, the great Roy Buchanan.
DGDecNV build 238 will not run but 236/237 do
Not for the meek. Play it loud. Close your eyes.
- Aleron Ives
- Posts: 126
- Joined: Fri May 31, 2013 8:36 pm
DGDecNV build 238 will not run but 236/237 do
Now that DGDecNV is free, could you perhaps take the latest version that can reasonably be expected to work on XP and add the binary to the download page as "DGDecNV Windows XP Final"? I'm also on Windows 7 these days, but I always appreciate when developers keep around older binaries with a "this is the final version to support Windows version x" disclaimer, in addition to the binaries that target newer Windows versions.
DGDecNV build 238 will not run but 236/237 do
That would be difficult as we no longer have any WinXP machines that could be used to determine the last working version. Regardless, we do not want to contribute to the prolonged death rattles of XP.
- Aleron Ives
- Posts: 126
- Joined: Fri May 31, 2013 8:36 pm
DGDecNV build 238 will not run but 236/237 do
I guess there are driver limitations, too. Is there a minimum nVidia driver version required for DGDecNV 2053? If there is, I don't see it listed on the main site. I'm still using 2048 with the same drivers I've been using since 2014, as everything "just works", so I'm a bit afraid to try 2053. ^^;
DGDecNV build 238 will not run but 236/237 do
There is an insane number of bug fixes and feature additions in 238 versus the ancient 2048. You sound like one of those XP diehards. Note that 2053 is no more; the most up-to-date is build 238. Everybody has been successfully using 2053 for years. 238 is basically 2053 on steroids.
Tell us what card you have and what driver version you are running.
There's no need to be afraid. You can always go back to your current driver version and 2048 if things go sideways (which I don't anticipate).
And upgrade to a recent Avisynth+ while you are at it.
Even buggy whips became obsolete at some point.
Tell us what card you have and what driver version you are running.
There's no need to be afraid. You can always go back to your current driver version and 2048 if things go sideways (which I don't anticipate).
And upgrade to a recent Avisynth+ while you are at it.
Even buggy whips became obsolete at some point.
- Aleron Ives
- Posts: 126
- Joined: Fri May 31, 2013 8:36 pm
DGDecNV build 238 will not run but 236/237 do
I don't think I'm in quite the same boat as the XP diehards. I'm at least one lake over. I built this rig in 2014, got everything working, and haven't seen a major need to change things since then. "If it ain't broke, don't fix it" is an excellent motto for computer usage if you want to avoid unnecessary reformatting.
I'm using my trusty GTX 760 on driver 326.80. I couldn't update beyond that driver, because later drivers introduced a bug in Kepler cards that tanked OpenCL performance. I'm not sure if nVidia ever fixed it; as of 2015 there was no fix besides avoiding the broken driver versions, so I never updated again.
I'm using my trusty GTX 760 on driver 326.80. I couldn't update beyond that driver, because later drivers introduced a bug in Kepler cards that tanked OpenCL performance. I'm not sure if nVidia ever fixed it; as of 2015 there was no fix besides avoiding the broken driver versions, so I never updated again.
Thanks. I made it myself. Come to think of it, I probably used DGAVCDec, as my old XP rig had a GeForce 6800 and wasn't compatible with DGDecNV.
- Wonder Woman
- Posts: 58
- Joined: Sun Feb 07, 2021 10:46 am
DGDecNV build 238 will not run but 236/237 do
"If it ain't broke, don't fix it."
-- Ann Landers
You sound so down-to-earth, pragmatic. Wanna hang out?
-- Ann Landers
You sound so down-to-earth, pragmatic. Wanna hang out?
DGDecNV build 238 will not run but 236/237 do
WW is getting desperate. Balti hit it and quit it, now...where are all the good men?