There must be a way out, please help
arlynet_8f82a640ae
Posts: 20
Sorry to bother again but I got myself a nice Geforce 770 4096 and I immediately updated the driver online. Once again, my old driver from Nvidia (331)once replaced by a new one (340) something got crushed in my prefs or watever, since Dazstudio 4.6 pro refuses to open, pretending that I use a 1.1 version of Open Gl instead of a 1.3 (actually I am on 4.4 but for some reason Daz does not seem to be aware of it and wont open).
Just to make a test, I downloaded and tried a version of the Furryball Renderer which provices a benchmark : with nvidia driver 331 this ultra recent renderer will refuse to raytrace. With the 340 driver everything scores normal (whereas Daz gives up with this very version that seems ok elsewhere, when starting the program).
It's difficult to figure out why .. Any hingt ? Thanks
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Not got that version, I fall in between your two versions with 337.88 for my GTX680Ms and have no issue with Daz Studio, nor Octane. A qucik check reminds me that there is an upgrade possible for me, to 340.52. Which, I think, I may pass on for now!
It may be a bad driver, or it may be that you have dual graphics (NVIDIA card + Intel chip) and it's defaulting to the Intel. The NVIDIA drivers should install NVIDIA Control Panel which lets you specify the default graphics adapter and override the default for specific programs.
I have the same card (EVGA FTW version). I'm running on 340.52 version of the drivers no problem. Uninstall your driver completely, reboot your pc, then redownload and reinstall the driver using the clean install option.
If, as Mike brought up, Daz is recognizing an intel graphics chip instead of the card, do the following-
Open up your Nvidia Control Panel and go to Manage 3D Settings > Program Settings > Find or Add Daz Studio in the drop down > Select the 770 as the default card to use.
The easiest thing to do, if this is the case, is to disable the intel graphics altogether from your bios.
What they said...
FWIW 340.52 works fine on my GTX765M on Windows 8.1 x64 with the current Daz 4.6 x64 beta. So I think the likelihood is high you can get it running under 340.52 rather than having to revert to an older version.
Thanks for your suggestions but I am afraid that there is no intel graphic chip on the motherboard. I tried as well to designate the Daz program in the 3D preferences of the Nvidia driver, everywhere I could I have chosen the specific nvidia GPU - no luck. (at least with Daz I should say, all the rest is working like a charm). I keep inquiring but i welcome
Go to C:\Users\You\AppData\Roaming\DAZ 3D\Studio4 and open the log.txt file, then find the section like this:
and paste it here. (AppData is hidden by default - in Windows 8 you can show hidden files and folders from the View tab of the ribbon bar, in Vista and 7 you need to enable hidden files and folders in the Folder Options Control Panel applet.)
You are right, it seems that Daz sticks to some "microsoft provided" version of openGL. Why ? And how do I obtain that Daz takes in account my 4.4 nvidia version ? (Thanks)
now to make sure that my system was using nvidia 4.4 I have attached the diagnosis by some tool that I found on the net
Supported OpenGL extensions:
GL_WIN_swap_hint
GL_EXT_bgra
GL_EXT_paletted_texture
OpenGL features for current hardware:
OpenGL provider: Microsoft Corporation
OpenGL renderer: GDI Generic
OpenGL version: 1.1.0
Maximum number of lights: 8
Number of auxiliary buffers: 0
Number of texture units: 0
Depth buffer bit resolution: 32
Maximum OpenGL texture size: 1024 x 1024
Current OpenGL Texture Quality Setting: Good Performance
RGBA color bitplane resolutions: 8 8 8 0
GLSL not supported
Shadow mapping not supported
VBO not supported
Error while initializing OpenGL extensions: énumérant non valide
OpenGL version on this machine not supported, DAZ Studio can not start!
DAZ Studio failed to startup.
--------------- DAZ Studio 4.6.3.52 exited ------------------
What happened when you tried to set 3D preferences for DAZ Studio?
Nothing happened, I have set the nvidia prefs to my graphic card, i have designated Daz as a specific program to be linked to the CGU , nothing.
Is there any mean to re-route my Daz towards my real openGL driver ?
Forgive me for belaboring the point, but I just want to make sure I'm clear.
1) Does the NVIDIA Control Panel show a choice of 2 graphics processors?
2) If so, does NVIDIA Control Panel show DAZ Studio set to use the NVIDIA card?
3) Did you update the drivers on the NVIDIA website, or are you using the drivers that came with the system?
No the Nvidia Control Panel shows only one.
Il did update the drivers online at nvidia, so far no luck, not even with a prerelease of 340.82.
I uninstalled and reinstalled DAz, the driver, nothing.
Daz seems stuck to that older version of open gl that came from nowhere.
here is a benchmark of my openGL (the latest, 4.5, it comes with the Beta driver by Nvidia)
re_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control
-----------------------------------------------------------------------
Graphics Adapter: NVIDIA GeForce GTX 770
Manufacturer: NVIDIA Corporation
GL Version: 4.5.0 NVIDIA 340.82
Resolution: 1200 X 1920 X 32 bpp
Driver version:
-----------------------------------------------------------------------
Windows Version: Windows 7 Home Premium
CPU: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz(3310MHz)
Physical Memory Usage: 4095/4095MB
Virtual Memory Usage: 4095/4095MB
If you look in control panel/device manager you should be able to see if there are multiple drivers loaded.
Try uninstalling the Forceware drivers, reboot, and clean install the official Geforce drivers.
http://www.geforce.com/drivers
Of course in Device manager only one shows up, Nvidia.I see no forceware in my system, I uninstalled the whole package in safe mode, reinstalled in safe mode the official 340.52 driver instead of the beta 82. I must say that every other piece of software seems to highly benefit of this new version of the driver, but DAZ simply rejects it.
Remember that it accepts version 331 that was equipped with OpenGL 3. Seems definitely that the picky sofware with open GL is DAZ. Blender works beautifully, same with Sketchup.
Does the 340.52 allow daz to use 4.4?
Sorry everybody, but he dev team just told me that it was "a known issue" and that I had to roll back to my last year nvidia driver. I would like to hear from stoltenkamp again who pretends to have and operative 340 nvidia driver with " the current Daz 4.6 x64 beta" . Where do I get this beta ? Do I have the last 4.6 pro ? Thanks
The beta has to be downloaded through DIM.
For what it's worth, I have both the current beta and the release versions running the 340 driver and both are using OGL 4.4, so I'm not sure why they would say it's a known issue, when it does work. Unless it depends on other factors.
That's what I would vote for.
That's what I would vote for.
I'm assuming, just not sure what. We're running the same card. Mine's the EVGA FTW version, not sure what the OP's running.
Right. But I'm not referring "only" to the graphic hardware. Who knows what else is different between the two systems? There could be other conflicts not yet known, such as different levels of Windows patches applied or not applied, a difference in motherboard BIOSs, or chipset drivers that are from completely different manufacturers.
Somebody said the words "pretends to run" in a prior post and I thought this was a little bit shortsighted to say. There's nothing to be gained by somebody lying about their setup here.
Don't know if it will help but just seen there has been an update to 344.11 (I don't have this yet, so cannot comment on what effect if any it will have).
Oh believe me other hardware can cause riddiculous conflicts
my wacom tablet seems to be the culprit making my mouse pointer vanish sometimes in Daz studio even though not using it.
When I had a 3G internet dongle it made my DVD burner vanish
the OP could try unpluging all peripherals maybe and troubleshoot but I suspect tech support has already isolated the issue and are working on
To those interested I did not solve the problem but I think i have spotted the zone.
Suspecting It could be linked to a long term postponed update of the graphic routines in W7, I used another W7 from scratch, left it on trial, updated it with w update, then installed Saz Studio 4.6 right after the nvidia 344 driver, and it worked like a charm.
Thinking it might be due to the shift from 340 to 344, i went back to my first W7 on another disk, installed the new graphic driver, no luck. Then I thougt to myself, why not updating Windows as well as I did on the other side? Which I did. Long process, lots of restart, suspense, but the usual prompt wen on. (Blabla, you got opengl 1.1, you should get the 1.3 - but I got the 4.4, honey, and you don't seem to have your glasses on)
I think this daz installation is doomed.
Should I wipe everything out ouf the disk, including the content and the plugins, animate 2 and so on, to make a fresh start (painful) or could I count on some genius outthere to send me a hint (this includes the dev team of course) ?
Don't touch your DAZ installation or wipe your disk. (not yet)
There is a high probability that the new driver is not correctly installed and certainly because of some leftover installation from a previous driver in the registry
I had no problem till now with Nvidia Drivers. If I'm correct there is an option to make a clean install when manually installing the full driver package (I don't know for the online update)
By doing that it removes the old version before installing
There are a few things to check also : always elevate your rights when installing or uninstalling something => Right click and Run as Administrator
If that doesn't work you can try to wipe out completely the Nvidia driver with a tool called Display-driver-uninstaller. I had the same problem you had but with an ATI card. After it cleaned my system from AMD's driver and after a reboot and new installatiion, the problem was solved
http://www.guru3d.com/files-details/display-driver-uninstaller-download.html
Thanks a lot, i check this out and will give feedback.
Alas, I did uninstall in safe mode using display driver uninstaller, but so far no luck. I will try in addition a "clean" install from nvidia in administrator mode but it's difficult to understand why Das Studio should be the only program to grab a lost trace of an ancien graphic driver whereas all the other programs including octane, Furryball, etc are happy with the 4.4 opengl that is inside the driver.
As I suspected, a clean re-install under administrator mode gives the usual response from Daz Studio when starting. It keeps on requesting an OpenGL 1.3 ans does not open. Remember that the 331 nvidia driver worked on Daz a few days ago on this machine, and that another hardrive, on the same computer, with a copy of the same Windows 7 64, launches Daz Studio without problem using the driver 344, the most recent. Puzzling.Thanks anyway.
Did you ever solve this?
The reason i ask is that someone else with this same card found this issue:
"So as it turns out the culprit in my scenario was actually a particular plugin, dzrenderlibrary.dll . Removing it from my plugins folder allows Daz to load and--as far as I'm aware--operate as normal.
Anyone know what dzrenderlibrary.dll is responsible for? It sounds somewhat important, but I've not--yet--encountered any problems running Daz Studio without it."
http://www.daz3d.com/forums/discussion/35085/daz-studio-4-6-pro-crashes-at-launch-nvidea-geforce-770
I did solve it by getting rid, manually, of all the contents of the Daz Studio folders befor a reinstall.