Error exporting FBX from DS Pro 4.6.1.14 Beta 64 bits
cesar_monroy
Posts: 17
Error occurred while exporting file. See the log file for details.
Error exporting file: C Exception: Memory Access Violation - Attempted to read memory at address 0x00000000
Failed to export file: C:\Users\Public\Z Projects\People\Shayana\bb1.fbx
Unhandled exception during operation
Can anyone help with this? Thanks.
PS. I do know this error was caused by a non-conforming item. The guilty one can be some prop, a piece of wardrobe or even a skin mesh. Sometimes, the presence of 2-3 items is what produces the non-conforming error; others, the cause seems to be duplicate items and in some other instances, the cause is unknown (at least for me). Maybe a technical explanation -more tha the crypctic Memory Access Violation- would be helfulf.
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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
What OS are you using, and what are your computer specs?
What size is the Scene (number of items) that you are trying to export as FBX?
Hello Jimmy.
My PC box runs Windows 7 Ultimate 64 bits. Got inside it an AMD Athlon X2, 8 GB of RAM and a graphic card Radeon HD 6450. Scene contains one Genesis figure with some props. It renders fine, but it fails when trying to export it. Removing the Katana does the trick.
Hi Cesar
Its been a long time since I had this error, I've forgotten how I cured it.
It was either the location of the DS temp file or one of the FBX settings or was it one of the export rules?
I haven't been able to recreate it since, do you have you have the DS temp location on a different HDD than the system drive?
Hello Prixat.
I use DS basically as it came... No fiddling with the settings, no extensive customization, just the plain stuff. The temp folder should be wherever it was configured to be by default, as I have not tampared with those settings. FBX settings are plain also: just export model and props, no animation, no morps, no lights, no camera, only one rule to bake everything and use the binary 2012 version (not a real difference if I use previous versions, as far as I'm concerned). Thank you anyway.
I'd recommend moving the DS temp folder anyway, it will help with stability and speed generally.
I'll try your suggestion, Prixat. Thank you.
Hmm. I got to this post due to the same memory access violation string, but in different circumstances...
I just updated to 4.6 in the past week, and after playing with some new scenes to warm up, I returned to the project I started in my previous version of DAZ, but was not able to open it--or any other saved scene. Here's the relevant portion of the log:
Opening file avonlea - ddo pose approximation.daz...
Error setting pointers while reading file C:/Users/Owner/Documents/DAZ 3D/Studio/My Library/avonlea - ddo pose approximation.daz : C Exception: Memory Access Violation - Attempted to read memory at address 0x00000000
File read time: 0 min 1.1 sec.
Building Scene...
Ran tdlmake on image C:/Users/Owner/Documents/DAZ 3D/Studio/My Library/Runtime/Textures/Sarsa/Duo/6_M4V4LashesResource4.jpg
Ran tdlmake on image C:/Users/Owner/Documents/DAZ 3D/Studio/My Library/Runtime/Textures/Sarsa/Duo/3_V4Resource4.jpg
Ran tdlmake on image C:/Users/Owner/Documents/DAZ 3D/Studio/My Library/Runtime/Textures/Sarsa/Duo/5_V4Resource4.jpg
Ran tdlmake on image C:/Users/Owner/Documents/DAZ 3D/Studio/My Library/Runtime/Textures/Sarsa/Duo/3_V4Resource4B.jpg
Ran tdlmake on image C:/Users/Owner/Documents/DAZ 3D/Studio/My Library/Runtime/Textures/Sarsa/Duo/3_V4Resource4S.jpg
Ran tdlmake on image C:/Users/Owner/Documents/DAZ 3D/Studio/My Library/Runtime/Textures/Sarsa/Duo/4_V4Resource4.jpg
Ran tdlmake on image C:/Users/Owner/Documents/DAZ 3D/Studio/My Library/Runtime/Textures/Sarsa/Duo/4_V4Resource4S.jpg
Ran tdlmake on image C:/Users/Owner/Documents/DAZ 3D/Studio/My Library/Runtime/Textures/Sarsa/Duo/4_V4Resource4B.jpg
So, again, nothing appears to have actually loaded, and this was a single genesis figure in a basic nude texture. I have not been able to use most of my pose presets from the old version, but hoped I could get the pose from the old scene. Maybe relevant, maybe not. Anyway, here's the system info as well:
ASUS Notebook G72GX Series
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:7, Stepping:10 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1
Physical processor count: 2
Processor speed: 2527 MHz
Built-in memory: 6143 MB
Free memory: 961 MB
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Basic
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: False.
OpenGL Crash File: Not Detected.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce GTX 260M/PCIe/SSE2
Display: 2
I am happy enough with the improved performance I'm seeing in 4.6 to get over losing all of my presets, but it means I can never return to fix any project I've used DAZ in prior to this week. I'd really appreciate it if someone can explain what the problem is, and tell me if there's any hope of transferring all of my legacy work with me to 4.6. The install wiped out my older version, so there is no going back.
How do I keep moving forward?
If you want to go back, uninstall de beta version and install the previous one.
Funny.
Are you saying there is no way to import or convert .daz scenes for or in DAZ 4.6? If so, they really should have warned us up front. I would have at least made an effort to save presets of everything I could. Of course, I have had issues with old presets too, so...
Is there anything from my older version that I can be sure carries over, or do I go and download and reinstall everything I ever got for DAZ and write off all my old work?
As I said before, the performance improvement in 4.6 is about the only thing encouraging me to continue working with DAZ. It's not really worth going back, so I'm interested in knowing how much will carry forward.
Thanks.
To be honest with you, I didn't noticed any "improvement" when using the new beta. I had the same problems exporting files as I had with the previous version, so whatever the goddies beta has, I found none... So, I rolled back to the stable version and maybe will try the new one some other time.
I'm still not sure what the exact cause of the error is. I've been digging through the forums for tips and hints, and discovered the Install Manager was installing content to a new location, while DAZ has been using the original library. Much of my time has been spent uninstalling (yep, had to do it after all) and reinstalling to the correct paths. That fixed my, "I don't see any of the new content, and my old content is fsked!" issue, as far as I've been able to confirm. Possibly related, the next problem I ran into was DAZ refusing to load Genesis, because it was pointed at the .dsf version. The new install in the right place let me point it at the .duf version, and get it loading again.
Possibly, the error I came here to figure out is related to the format change. I mean, the initial issue was obviously with a legacy .daz scene, but that scene would be pointing to .dsf resources. I don't know if the extension is all that changed, or if the structure and format of the file is inherently incompatible. I've flagged some posts and articles on importing legacy content, but have not had a chance to review them. If I get a solid answer, or a workable fix, I'll come back and share it.
JadeRail, do you mind pointing me at a proper MAP procedure? I used the Install Manager because it was supposed to automatically resolve all my updates; they weren't clear on the fact that the statement only applies to the current generation and newer products. I may have bookmarked a page with that info, but I have not read anything I recognized as a fix for this issue, or the former "My Stuff" presets.
Edit: JadeRail, I came across a post of yours where you explain how to set the correct paths in the content directory manager and confirmed that DAZ is using the path I expected. I have at least one .daz scene load without problems, using an M4 and V4 model. The last scene I created using a Genesis model, saved as .daz opened successfully, so I'll run through them backward until the problem appears again. If nothing fails, I'll assume that it was fixed by uninstalling and reinstalling.
Thanks!
Did you finally figure out what the issue was? I had the same issue but I found a resolution to it. MAKE SURE ALL YOUR ITEMS ARE CONFORMED TO YOUR MODEL NOT TO OTHER ITEMS.
This caused me a lot of pain but that was the problem.
I encountered a something like similar problem.
1. Creating in 3DS max 2012 new file with several objects
2. Exporting one or more of them as DAE
3. Import in DS work perfect
4. Continue to work with scene in 3DS max
5. Exporting one or more of them as DAE again
6. Import that DAE in 3DS max 2012 and re-exporting like DAE again
7. Import in DS work perfect again
It's... strange...
I know this thread is older, but this is exactly what solved the problem for me. I was trying to put the tankini under the magnus jacket and had parented the jacket to the tankini for smoothing purposes. Thank you for saving me a ton of troubleshooting time.