Jump to content

Search the Community

Showing results for tags 'crash'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Lounge/General chat
    • Education
    • Jobs
    • Marketplace
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering
    • Compositing
    • Games
    • Tools (HDA's etc.)
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Found 40 results

  1. Trouble with exploding RBD SIM

    Hi all, I'm still pretty new to Houdini, but I offered to do my friend a favor by attempting to sim a spaceship crash for his short sci film. It was more of an excuse to learn RBDs in Houdini than anything else, but now that I've invested this much time I really want to make it work. Anyhow, I started with Steven Knipping's Applied Houdini Rigids III Vehicle Destruction course and once I finished that, I tried replacing the supplied helicopter model with a spaceship that I modeled in C4D using a Kitbash kit, so I imagine the geometry shouldn't be an issue. It would appear that I'm very close to getting a workable sim because I got it crashing and denting with the original animation that I set up for the ship. However, I've been running into a bit of a snag if I change the crash animation. For whatever reason, if I move the ship at all to match any of the tracked alembic cameras I was sent, either by changing the keyframes of the crash itself, or even by simply attaching the entire animation to another null and moving it in the scene, the ship totally blows up. You can see what I mean in the last 3 previews found in VFTV\render of the attached project folder. Maybe I'm missing something very basic, but as far as I can tell this shouldn't be happening, as my understanding is that the hard constraints I'm using on most of the ship aren't supposed to break unless I tell them to in the art directed cuts section of the frac SOP. Anyway, the first preview in the VFTV\render folder shows that the sim more or less works with the camera matching but without denting, and the second shows the crash with denting but with no camera matching. But, for whatever reason I couldn't get the source tracked cameras working directly in Houdini, so I took them into C4D first, changed the resolution and alembic camera scale, and exported them at .01cm from C4D, and after that they seemed to line up in Houdini once I changed the camera view resolution to match. However, my troubleshooting brain is telling me that I might've messed something up during this process and perhaps the explosion is due to mismatching scene/camera scale issues with the alembic cameras that the tracking artist sent causing the sim to be calculated differently. I'm not even sure if the C4D camera scale option affects the sim in Houdini and/or C4D, but scene scale certainly does, and if the imported camera scale is messing with scene scale, then maybe that's the problem. That said, I don't think that's the reason, because if I leave the original animation alone it seems to sim fine even with the new cameras. And, I believe I'm matching the scale correctly and using the right conversion which is supposed to be .01cm from C4D to Houdini. I've also messed around with exporting different camera scales and scene scales out of C4D and importing the alembics back into Houdini using several different methods, all with the same result. But, I realize it might help me to know more about which software each shot was tracked in, so I'm double checking with the guy at Framestore, who did the tracks, regarding the scene scale conversions. I was thinking Syntheyes might be different from Nuke for example. That said, I would be eternally grateful if anyone was willing to look at the project and let me know what they think the problem could be. My hope is it's something stupid on my part, and not some overly complex issue. Here's a Dropbox link to a reduced version of the project with all the assets VFTV_Smoldering_Wreckage_1_200813_v001.hiplc
  2. Particle Sim Crashing

    I've tried caching out a particle sim multiple times each time it crashes at frame 190 of 240 and gives this error. Does anyone have any idea what this could be? crashLog.txt
  3. Hi guy. I had been working with redshift for over a month already and I am in the middle of a proyect. Suddenly when I open the proyect EVERYTHHING failes. There isn´t a single redshift node working: This is my env: PATH = "C:/ProgramData/Redshift/bin;$PATH"<font></font>" HOUDINI_PATH = "C:/ProgramData/Redshift/Plugins/Houdini/17.5.173;&" It looks like it uninstalled itself somehow. I really don´t know what did I do. It just stopped working from one day to another. I tried resenting the pc and reinstalling redshift. I hope you can help me. Thank you
  4. I left a TOPs network rendering some camera angles, but it's stopped with missing frames in one of the sequences (1-112 where it should be 1-144) Dirty and cook returns done. The caveat is I have 'Cook frames as single work item' on for post-processing nodes (ffmpeg and then some python in this case), when I deselect this I get all the frames and it picks up. How can I get it to check the frames, discover which are missing and pick up where it left off? OR would it be better to let it cook individual frames and then group the output by filename and push that into ffmeg?
  5. Hey, Anyone else having an issue with 17.5.258, where redshift 17.5.229 rendering works fine... but my flipbooks (Mplay) crash? I can render with Mplay but when I go to flipbook anything it leaks mem and them flipbook crashes saying it can't display images. If I remove the env variable pointing to the taskbar, flipbooks work? if I use an earlier redshift plugin version (i.e. 17.0.506), the self and flipbooks work fine... but there isn't the same functionality. There doesn't seem to have the RS proxy output. Please let me know if you have run into this or an issue similar. Thanks
  6. What is the proper way to install the latest Nvidia drivers and CUDA stuff in Ubuntu? I'm currently running Ubuntu 16.04 with GTX 970. I installed 430 version using PPA but the Houdini keep crashing on startup. Then I downloaded the latest NVIDIA-Linux-x86_64-430.40.run from Nvidia site and ran but the computer started having black screen after that. Now I purged the the drivers and rollbacked to 384. I need the latest nvidia drivers because I wanted to test the arnold GPU rendering. i would greatly appreciate any help.
  7. Mosaic node crashing Houdini

    Hi, I'm trying to mosaic a seires of 64 textures with 1 image per row, images are 512x1 pixel, the expected output is a 512x64 pixel texture. The problem is as soon as i join my file import node into the mosaic, I get a hard crash to desktop. This only happens with textures over 256 pixels wide. Any assistance is appreciated.
  8. Hello everyone, My Houdini crashes when I launch a Flipbook. No idea what is happening... I have a dual boot machine. On the other Disk I have windows, and Flipbook is fine there. My OS: Ubuntu 18.0.4 LTS. My Houdini version: 17.5.295.
  9. Hello, please help me. I can't get running Houdini 17.0.352 on my laptop (windows 8.1.) After install it was working properly, but after restart, everytime I'll do an object and turn on smooth shaded it will crash immediately (wireframe works). I've tried everything I could: - googling solutions - update all drivers - reinstall houdini - try to install windows 10 (wasn't possible because of my laptop) crash report: Qt Warn: Warning: QT_DEVICE_PIXEL_RATIO is deprecated. Instead use: QT_AUTO_SCREEN_SCALE_FACTOR to enable platform plugin controlled per-screen factors. QT_SCREEN_SCALE_FACTORS to set per-screen factors. QT_SCALE_FACTOR to set the application global scale factor. 4008: Fatal error: Segmentation fault Saving application data to CUsers/KUBAN_~1/AppData/Local/Temp/houdini_temp/crash.untitled.kuban_000_4008.hiplc
  10. Hey magicians, I'm having crashes (houdini directly closes without any message) when rendering. This happens in random frames, and in some of the setups. I checked the log and seems to be a GPU issue, I have 3 Geforce 980 Ti. I will contact their support, but posting here just in case anybody knows a solution. Cheers
  11. Hello there. First at all, I'm not English people. So please forgive for my English. I have a problem with Houdini 17 (Apprentice, 17.0.416) . I fail every rendering even on "Render View" rendering. Error message is this. Failed to save output to file "Traceback (most recent call last): File "/Applications/Houdini/Houdini17.0.459/Frameworks/Houdini.framework/Versions/Current/Resources/houdini/soho/python2.7/IFD.py", line 102, in if not soho.initialize(now, camera, options): File "/Applications/Houdini/Houdini17.0.459/Frameworks/Houdini.framework/Versions/Current/Resources/houdini/soho/python2.7/soho.py", line 201, in initialize _registerWranglers() File "/Applications/Houdini/Houdini17.0.459/Frameworks/Houdini.framework/Versions/Current/Resources/houdini/soho/python2.7/soho.py", line 169, in _registerWranglers filelist = glob.glob(unicode(path + '/wranglers/*.py')) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 25: ordinal not in range(128) ". I'm using mac, 2.6GHz Core i7, 16GB RAM, Radeon Pro 450 2048MB. This problem doesn't occur at my Windows PC.
  12. Auto UV crashing?

    Hi auto UV is constantly crashing in H16.5 and H17. working wth the v1.72 of the gamedev tools. Am I the only one? I want to quickly do it on a car mesh around 600.000 polygons. thnx
  13. Hi everyone! I'm kinda new to Houdini and use it with UE4. My Digital Asset crashes all the time though so I thought I'll debug it with the Houdini Engine Debugger. This works well and actually is pretty awesome. When I reproduce my crash in UE4, the connection gets closed and the Houdini Console shows the following errors: Thrift: Mon Oct 29 18:09:38 2018 TPipe ::GetOverlappedResult errored GLE=errno = 109 Thrift: Mon Oct 29 18:09:38 2018 TConnectedClient died: TPipe: GetOverlappedResult failed But where to go from here? Is there a way to find out what node crashed? Or how should i proceed to narrow down the problem? Is there any kind of log file I could check? If you need more information, please let me know! Thanks for you help in advance! best, Ron
  14. Hi, I have a problem with running Houdini since I have my new computer. I already contacted support but could't figure out the problem yet. I hope somebody met with this problem or have some idea for a solution. So houdini is crashing after a few second, I cannot do anything with it. I made some test, seems like it crashing mostly when I press tab and start writing a node. any node. When I just open it it doesn't die instantly, but as soon as I try to do something it just crashes. Doesnt matter if I open a clean scene or open a scene I already have. Recently I got the following error message: 6440: Fatal error: segmentation fault. But in the past sometimes it was just quiting without any message. I had the smae problem since I have this laptop, with H 16.5, but somewhy one of the daily built was kind of working, crashing less frequently, but since H 17 came out I tried that, and it do the same thing. I tried the following things: Reinstalled Houdini many times, different versions, different drives, tried it all. Checked and updated videocard drivers, windows updates the latest (win 10, NOT developer/insider version), cleared registry. Checked Rams, videocard with stress test. and anyway all of the other software running without problem. Also tried turn off every other sofware while running houdini but its all the same. The laptop: MSI laptop with 6core i8, 32gb ram, geforce 1070. So that shouldnt be the problem. I clueless now, I have this problem since months. I would really appreciate any help. Thanks!
  15. Anyone else feel like 16.5 crashes more frequently than previous builds? One way which can be replicated is hitting esc whilst creating a flipbook. This is quite annoying. 16.5.405, CentOS 7
  16. Hey there, Got an interesting crash/not responsive on windows here the other day. Its a fluid sim. Intel Xeon W-2195 Quadro p2000 128GB RAM Crash log: Crash report from ; Houdini FX Version 16.5.268 [Windows 10.0.10586] Uptime 31170 seconds Wed Jul 25 00:04:10 2018 Caught signal 11 Traceback from 11220 ThreadId=0x00002da4 CURRENT THREAD 11684 +0xacffdc69 [GA_ListTypeRef<__int64,__int64,__int64>::ListTypeData::copy] +0xad398b46 [GA_ListType<__int64,__int64,__int64>::harden] +0xad3a23d9 [GA_IndexMap::defragment] +0xad383b0f [GA_Detail::defragment] +0xad383753 [GA_Detail::defragment] +0xa8f9db99 [GAS_SeedMarkers::seedMarkers] +0xa8f9fc33 [GAS_SeedMarkers::solveGasSubclass] +0xa8fc70fc [GAS_SubSolver::solveGas] +0xa8fc7308 [GAS_SubSolver::solveObjectsSubclass] +0xb18323f4 [SIM_Solver::solveObjects] +0xa8eb5ac7 [GAS_IntermittentSolve::solveObjectsSubclass] +0xb18323f4 [SIM_Solver::solveObjects] +0xb1839520 [SIM_SolverEnable::solveObjectsSubclass] +0xb18323f4 [SIM_Solver::solveObjects] +0xb1839520 [SIM_SolverEnable::solveObjectsSubclass] +0xb18323f4 [SIM_Solver::solveObjects] +0xa8fcaac3 [GAS_SubStep::solveObjectsSubclass] +0xb18323f4 [SIM_Solver::solveObjects] +0xb183a4f7 [SIM_SolverMulti::solveObjectsSubclass] +0xb18323f4 [SIM_Solver::solveObjects] +0xb16f9f53 [SIM_Engine::doSimulationStepForMetaObject] +0xb16f9730 [SIM_Engine::doSimulationStep] +0xb16fef11 [SIM_Engine::setSimulationTime] +0xb1a74fd2 [DOP_Parent::setDOPTimeSubclass] +0xb24160d6 [OBJ_DopNet::setDOPTimeSubclass] +0xb1a74db9 [DOP_Parent::setDOPTime] +0xa9a020f2 [SOP_DopImport::getDOPParent] +0xa9a063db [SOP_DopImport::initializeObjectInfo] +0xa9a00e75 [SOP_DopImport::cookMySop] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xc01f87f2 [OP_Node::internalCookInput] +0xc01fca2a [OP_Node::lockInput] +0xae641520 [SOP_Node::lockInput] +0xc0104bb1 [OP_AutoLockInputs::lockInput] +0xae6394d2 [SOP_Node::cookGuideList] +0xae32278e [SOP_NodeVerb::cookInputs] +0xae63b2ff [SOP_Node::cookMyselfAsVerb] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xc01f87f2 [OP_Node::internalCookInput] +0xc01fca2a [OP_Node::lockInput] +0xae641520 [SOP_Node::lockInput] +0xae7c03f5 [SOP_Switch::cookMySop] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xc01f87f2 [OP_Node::internalCookInput] +0xc01fcb1b [OP_Node::lockInputs] +0xae641726 [SOP_Node::lockInputs] +0xae65430b [SOP_Null::cookMySop] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xae631562 [SOP_UndoModel::operator=] +0xae63e390 [SOP_Node::getCookedGeoHandle] +0xae5a7290 [SOP_ForEach::cookMySop] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xc01f87f2 [OP_Node::internalCookInput] +0xc01fca2a [OP_Node::lockInput] +0xae641520 [SOP_Node::lockInput] +0xae7c03f5 [SOP_Switch::cookMySop] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xc01f87f2 [OP_Node::internalCookInput] +0xc01fca2a [OP_Node::lockInput] +0xae641520 [SOP_Node::lockInput] +0xc0104bb1 [OP_AutoLockInputs::lockInput] +0xae6394d2 [SOP_Node::cookGuideList] +0xae32278e [SOP_NodeVerb::cookInputs] +0xae63b2ff [SOP_Node::cookMyselfAsVerb] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xc01f87f2 [OP_Node::internalCookInput] +0xc01fca2a [OP_Node::lockInput] +0xae641520 [SOP_Node::lockInput] +0xae5a75fa [SOP_ForEach::cookMySop] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xc01f87f2 [OP_Node::internalCookInput] +0xc01fca2a [OP_Node::lockInput] +0xae641520 [SOP_Node::lockInput] +0xae7c03f5 [SOP_Switch::cookMySop] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xc01f87f2 [OP_Node::internalCookInput] +0xc01fca2a [OP_Node::lockInput] +0xae641520 [SOP_Node::lockInput] +0xc0104bb1 [OP_AutoLockInputs::lockInput] +0xae6394d2 [SOP_Node::cookGuideList] +0xae32278e [SOP_NodeVerb::cookInputs] +0xae63b2ff [SOP_Node::cookMyselfAsVerb] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xc01f87f2 [OP_Node::internalCookInput] +0xc01fca2a [OP_Node::lockInput] +0xae641520 [SOP_Node::lockInput] +0xae7c03f5 [SOP_Switch::cookMySop] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox] +0xc01dff94 [OP_Node::cook] +0xae631562 [SOP_UndoModel::operator=] +0xae63e390 [SOP_Node::getCookedGeoHandle] +0xae7ba4f1 [SOP_SubNet::cookMySop] +0xae63af93 [SOP_Node::cookMe] +0xc01d4860 [OP_ConnectorId::operator<] +0xc01cfa3e [OP_NetworkBoxList::saveSingleNetworkBox]
  17. Hi , I am building currently building an HDA with an important interface (lots of tabs and multiParm list inside multiParm list .. ) so I wanted to use python in "Menu Script" to list a string array stored in the detail attribute to populate on of my ordered menu, after I finally got it to work on a null to experiment then I tried to replace my previous ordered menu with manually typed string with the new one using python script and houdini crashes each time I try. What's weird is that I am able to read the channel and access the value with no problem outside the HDA. Does anyone knows why this is happening, am I missing something here ? Edit : It seems that when I try to return the string inside the HDA, it gives me -1, but even if I just print that value, houdini still crashes and why it return that value only inside the HDA ? Also when I enable "Use Menu Item Token as Value" I am able to return the corresponding ID of my selection without crash, but I want the string value of course. The python script I use : node = hou.pwd() geo = node.geometry() menu = [] data_list = geo.stringListAttribValue("data_list") for data in data_list: menu.append(data) menu.append(data) return menu
  18. [SOLVED] Hello. I just got a new motherboard, cpu and ram cards and now Houdini will crash when simulating. Sometimes it's just the program, sometimes I get the blue screen with error codes SYSTEM_SERVICE_EXCEPTION and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Everything was working fine with the old hardware and I could play the sim all the way through. The sim is much faster with the new hardware except it will crash eventually. The sim does slow down before crashing, but I'm only using about 40% of my total ram. Everything with the new hardware seems fine otherwise. Here are the hardware specs: Motherboard: From ASUS Z87-K to ASUS Z370-A CPU: i7 3770k to i7 8700k RAM: XPG 16GB DDR3 to PNY 16GB DDR4 PSU: Seasonic M12II-750 Bronze I have the latest drivers for my graphics card installed. I installed the hardware myself and am a total noob, FYI. I wouldn't know if my PSU is good enough for the hardware and I assumed it doesn't matter which slots each hard drive gets plugged into, so I plugged them in somewhat randomly, but it's all working. There's not much else I can think of where I might have screwed up, other than plugging the fans into opposite ports from what they were before (CHA_FAN1 is now in CHA_FAN2) or using too little/too much thermal paste... and the new hardware isn't compatible with any of the old hardware and vise versa so I can't test it that way. Thanks for reading and for any help.
  19. Hello Folks, My houdini is keep crashing even if file is empty. Any Thoughts ?:( Thanks Rajwinder Cheema System Model: Alienware Area-51 R5 BIOS: 1.1.10 Processor: Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz (16 CPUs), ~3.6GHz Memory: 32768MB RAM Card name: NVIDIA GeForce GTX 1070 Manufacturer: NVIDIA Chip type: GeForce GTX 1070
  20. Nobody else is having this issue on Windows 10? Since 16.5.405 up Houdini just crashes for me on start up. marking some segmentation error. I updated my nvidia drivers and still same issue! Nico.
  21. Hello, i am currently working on my final student projet where i make a plane crash with Houdini. I base the workflow of this project around the RIGIDS III tutorial by Steven Knipping. Everything is working fine until i bring in a simple glue constraint, and when the simulation gets activated at a said frame the simulation simply does not happen. It works when i disconnect/disable the constraint. I already tried to unpack the alembics upon importation with the alembic node but that didnt change anything. What is weird is that everything was working fine when i used the model given with the course. I haven't really found anything that helped me online, so hopefully one of you can help me with this issue, i would appreciate it A LOT. I will attach the files down below. Thank you ! plane_sim.rar
  22. MPlay Crashing...

    Hi! For some odd reason after I create a flipbook, I click file>export>video for windows 64 bit, and that crashes. It started doing this when I updated to Houdini 16.5 from 16. Anyone have any ideas why this would happen? If I do video for windows 32 bit, it works. I used to be able to do for 64 bit in houdini 16. thanks
  23. Hi guys! I have a question, and problem for my, the question is that I'm burning a simulation of simulation of Pyro, but Houdini crashed in the middle simulation, the problem is how I reload the simulation in the point that houdini crash? Thanks, I sorry my english no is very good:)
  24. Opening one scene I get a 'Load failed for... Unexpected end of .hip file' message. The hip file does open but most of the nodes are missing.. Does anyone know why this is? Is there a way to fix the hip file? The previous two versions are also corrupt but the one before that is fine. I can't think of anything that might have caused it. I updated from Arnold4 to Arnold5 and its possible that happened between those versions but my other hip files seem to be fine..
  25. Hey, guys! I'm a bit flummoxed as I've been exporting Alembic files from Houdini to use in 3D Studio Max for a while with no issues. But I've been struggling with a particular file all afternoon that's causing Max to crash. I've dealt with alembic files at least twice as large as the one in Max without any issue, so I doubt it's a size issue. I pulled the file back into Houdini and had no issues with the file in Houdini. I've tried both Ogawa and HDF5 formats. I've tried it on a couple different computers with the same results of Max crashing. It crashes when it gets about half way through both playback of the alembic as well as trying to export a Vray proxy mesh. Now, the effect in question does rely heavily on a boolean opperation from houdini to basically dissolve away a mesh, so could this have something to do with it? Any ideas?