Jump to content

MedicalByte

Members
  • Posts

    94
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by MedicalByte

  1. That is awesome! If I get any time I'll see about adding some options to the export script to allow for choosing the settings you want on export. I still remember scratching my head as to what some of those actually did haha.
  2. My apologies to everyone for the absence, especially to those of you who were relying on the scripts for your modeling. I have re-attached the files to the original post, as well as uploaded the files to the download center (http://www.emergency-planet.com/files/file/1205-blender-v3o-importexport-scripts/). Life has been busy (which is awesome!), thus the reason for my absence. I'll try to pay better attention to the thread should any issues arise in the future. Y'all take care.
  3. Version 1.0.0

    1,648 downloads

    This is an alternative download for the Blender V3O import/export scripts listed here: http://www.emergency-planet.com/topic/20108-blender-v3o-importexport-scripts/ Thanks goes to THVFD for his patience while I bugged him with all my Zmodeler2 questions. Requires Blender v2.7 These scripts are licensed under the GNU GPL v2.0 license (http://www.gnu.org/licenses/gpl-2.0.txt). Any use of these scripts and resulting actions is at the sole-risk of the user! I have done my best to ensure the scripts work as intended, but it's a good idea to keep back-up copies of models, textures, and any other data before use of these scripts. Current Features and Supported Functions: Import/Export Mesh Vertices/Faces Import/Export Materials Import/Export UV Mapping Code comments! (not the best, but I'll try to keep it somewhat documented for those who'd like to help improve it or understand what I've learned about the v3o format so far) Known Bugs: B001 - Can't export unless the model is uv unwrapped. - Fixed B002 - Can't export an imported .v3o model when a texture image fails to load. A texture image can fail to load when it doesn't exist in the imported .v3o file directory. Updates 20150225233000 Fixed Bug #001 Added a ton of comments and removed some uneeded code If y'all have any issues with the script or find any bugs, let me know here. If you are able to send me (via PM) any models/textures/.blend/.v3o files you are having issues with, I can hopefully recreate the specific bug on my end to work on a fix a little faster. If you have any feature requests, by all means ask! I can't guarantee anything but you never know till you try. Installation: 1. Extract the "io_mesh_v3o.zip" file. You should have a directory called "io_mesh_v3o" with four files inside. The file names are "__init__.py", "export_v3o.py", "import_v3o.py", and "License.txt". 2. Open the "%USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\2.73\" directory in Windows Explorer. 3. If it doesn't already exsist, you need to create a folder named "scripts". Inside of the scripts folder, create another folder called "addons". 4. Move the "io_mesh_v3o" folder into the "addons" directory. The four files referenced above should now be in the "%USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\2.73\scripts\addons\io_mesh_v3o" folder. 5. Start Blender up, and goto "File->User Preferences". 6. In the User Preferences window, goto the "Add-ons" section and search for "v3o". 7. Enable the v3o add-on by checking the box on the far right. You can save the setting by clicking "Save User Settings". That's it! The Import/Export options should now be available in the Blender File menu.
  4. My apologies for missing all the activity here. Thanks TH for helping people out! BogdanM, in regards to the scaling issue, there is a way to get the scaling to "stick". I didn't implement the auto-reset of the scaling vars in the scripts, but there is a way to do it. If you are still having the issue let me know and I can take a look when I get a spare moment. On the triangles vs quads issue, Newfoundking is correct, the v3o format is based on triangles, so the export script will convert all quads to triangles so it plays nicely in Emergency 4.
  5. It's a program called Blender (http://www.blender.org). It can be used for modeling any 3d object.Edit: well... that was unnecessary, sorry. Apparently I missed the rest of the posts (including THVFD'S answer).
  6. RFFD Engine 4 New model I created. (posted with permission from TH)
  7. That sounds pretty powerful (and very cool)! I've got the SDK downloading now to start checking it all out.
  8. Thanks for the update! I'll keep Steam loaded till the update is pushed in.
  9. Thanks! It should be a much more efficient process for Blender modelers now.
  10. I have been working on Blender V3O Import/Export scripts for the past few weeks and have achieved what I believe is a suitable state for beta release of the scripts. Thanks goes to THVFD for his patience while I bugged him with all my Zmodeler2 questions. Requires Blender v2.7 These scripts are licensed under the GNU GPL v2.0 license (http://www.gnu.org/licenses/gpl-2.0.txt). Any use of these scripts and resulting actions is at the sole-risk of the user! I have done my best to ensure the scripts work as intended, but it's a good idea to keep back-up copies of models, textures, and any other data before use of these scripts. Updates will be edited into this post. Current Features and Supported Functions: Import/Export Mesh Vertices/Faces Import/Export Materials Import/Export UV Mapping Code comments! (not the best, but I'll try to keep it somewhat documented for those who'd like to help improve it or understand what I've learned about the v3o format so far) Planned Features: Optional rotation on export Known Bugs: B001 - Can't export unless the model is uv unwrapped. - Fixed B002 - Can't export an imported .v3o model when a texture image fails to load. A texture image can fail to load when it doesn't exist in the imported .v3o file directory. Updates 20150225233000 Fixed Bug #001 Added a ton of comments and removed some uneeded code If y'all have any issues with the script or find any bugs, let me know here. If you are able to send me (via PM) any models/textures/.blend/.v3o files you are having issues with, I can hopefully recreate the specific bug on my end to work on a fix a little faster. If you have any feature requests, by all means ask! I can't guarantee anything but you never know till you try. Installation: 1. Extract the "io_mesh_v3o.zip" file. You should have a directory called "io_mesh_v3o" with four files inside. The file names are "__init__.py", "export_v3o.py", "import_v3o.py", and "License.txt". 2. Open the "%USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\2.73\" directory in Windows Explorer. 3. If it doesn't already exsist, you need to create a folder named "scripts". Inside of the scripts folder, create another folder called "addons". 4. Move the "io_mesh_v3o" folder into the "addons" directory. The four files referenced above should now be in the "%USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\2.73\scripts\addons\io_mesh_v3o" folder. 5. Start Blender up, and goto "File->User Preferences". 6. In the User Preferences window, goto the "Add-ons" section and search for "v3o". 7. Enable the v3o add-on by checking the box on the far right. You can save the setting by clicking "Save User Settings". That's it! The Import/Export options should now be available in the Blender File menu. b2_io_mesh_v3o.zip b2_io_mesh_v3o.zip
  11. A simple Google image search works fairly well too. Even if you can't find blueprints (which I recommend you don't limit yourself to them!) there are typcially good reference images you can model directly off of. This is especially useful for modeling curves and other details that aren't always shown or visible in a blueprint.
  12. It's possible you could recover the savegame file if it hasn't been overwritten yet. I'd recommend that you don't load any more data onto your disk and run photorec (http://www.cgsecurity.org/wiki/PhotoRec) off a flash drive if you can. The data recovery should also be offloaded to a separate external drive/flash drive to avoid overwriting sectors that haven't been searched yet. Even better would be to run it off a live cd (any linux distro, just install photorec after it boots if it doesn't come with it).
  13. Does your internet connection ever just "go away" and come back? If you have no problems with running the mods, I would suspect that perhaps there is something wrong with your (or his) connection to the internet. Does it disconnect if you play any other online multiplayer games? Are you connected via ethernet cable or wifi to your router? If the former, you might even try replacing the cable in case of a physical malfunction. Then again, they might be completely fine. You'd have to check on both ends of the connections (yours and his) as far as local networks and equipment go. Maybe you have a flapping interface, though, again, if you don't experience the same issues elsewhere, that may not be the case. Have you tried a complete re-install of Emergency 4? Perhaps a file is corrupted that is used in the MP mode of the game (totally random guess). Just throwing ideas out to check. I hope it works for you soon though, I know MP is one of the things I really like with Em4, so not getting to do it wouldn't be very fun for me.
  14. What are your pc specs? Does the game ever crash in single player? Specifically, does the mod you're running in MP crash in SP at all? (It looks like it's LA mod v2.1?)
  15. I've found this website to be pretty handy for getting a general idea of compatible parts and what-not. There are also plenty of custom-pc people there to get lots of good advice from. You could also check out previously built builds to get some ideas and tips. http://pcpartpicker.com/
  16. You didn't mention which version of Mayberry you had. In case it is v1.3, you might try the fix listed here: http://forum.emergency-planet.com/topic/19856-mayberry-county-13-mod-crash-issue/#entry287086
  17. I think the offline (not-signed-in) save game files are located here: C:\Users\<USER>\AppData\Roaming\Promotion Software GmbH\EMERGENCY 5\localAnd the online (signed-in) save game files are located here: C:\Users\<USER>\AppData\Roaming\Promotion Software GmbH\EMERGENCY 5\online
  18. If you don't see the quality settings in the option menu, you can manually edit the settings file here: C:\Users\<USER>\AppData\Roaming\Promotion Software GmbH\EMERGENCY 5\emergency_5_settings.jsonI believe you can change lines 25, 26, 27, 40, 41, 68, 69, and 70 where it says "ULTRA", "HIGH", or "MEDIUM" to "LOW" to manually set it to low settings. Lines 56 and 57 can be changed to "false" if set to "true". This should disable Fxaa and Depth of Field. Shadows can be disabled by setting line 45 to "false". Some users have reported noticable gains in FPS but a resulting lack in quality as well. Line 21 can be set to "false" to disable fullscreen if desired. Lines 22 and 23 can be changed to edit windowed and fullscreen resolutions. Regarding the RAM, remember that you need a 64-bit operating system (yours is 32-bit) to fully utilize any more RAM. Adding more RAM (even just 2GB) will not be very useful until you have an operating system capable of recognizing and using it.
  19. I would agree (to a degree) in many applications, but as I've said before, many reviews have stated that the RAM usage is exremely high for Em5, regardless of settings. Whether this is an optimization issue or otherwise, I don't know, but that's why I wouldn't be surprised to see the 4GB minimum enforced (at least for the time being). That being said, it's definitely worth a try in my opinion.
  20. I just noticed you only have 3GB of RAM. The minimum requirement is actually 4GB. The first log you uploaded has this error: [2014-12-11 22:29:56][QSF error] alBufferData: Out of MemoryI would think, given what I've personally seen with Emergency 5 and what others have reported, that you do not have enough RAM to properly run the game. Your system is also 32-bit, so you'd have to switch to a 64-bit computer to be able to utilize more RAM. Based on what little I know about the CPU in your PC, it should be 64-bit, but you'lll need to check the rest of your hardware as well. It's possible that all you would need to do is switch to a 64-bit version of Windows and add some more RAM (supposing your motherboard supports that as well).
  21. Can you upload your dxdiag file and log file? I wrote some instructions here: http://forum.emergency-planet.com/topic/19824-emergency-4-display-problem-steam-version/#entry286350 For the log file for Emergency 5 though, you need to look in the "C:\Users\<USER>\AppData\Roaming\Promotion Software GmbH\EMERGENCY 5\log\" directory. I think a new log file is written each time you start Emergency 5, so just upload whichever one (or more) are the crash-related ones. The filename format seems to be "qsf_YYYYMMDD_HHMMSS_LOG#.log".
  22. Alright, I have an idea for those who have the retail version of the game and are not able to install the patch. Just to clarify as well, the instructions do say to extract before installing. The official instructions mean unzip the zip file you downloaded, then run the executable "emergency5_update_1_2_1.exe" that was extracted. These instructions take it a second manual step further for those who are having issues with the installer itself. Disclaimer: I TAKE ABSOLUTELY NO RESPONSIBILITY FOR ANYTHING THAT YOU DO, FOLLOW, CAUSE TO HAPPEN, ETC. BY FOLLOWING, NOT FOLLOWING, OR MODIFYING AND FOLLOWING WHAT I HAVE WRITTEN BELOW. YOU ARE FULLY RESPONSIBLE FOR ANY AND ALL DAMAGES TO YOUR COMPUTER(S), FILE(S), ETC. YOU FULLY AGREE THAT YOU ARE SOLELY RESPONSIBLE FOR ANY AND ALL EVENTS, DAMAGES, ETC. THAT OCCUR OR ARE IN ANY WAY RELATED TO THIS GUIDE. Now that that's out of the way, here's my idea as to what y'all can do. Keep in mind this has NOT been tested by me (or anyone I know), so you are, in effect, merely testing to see if it does work. 1. Uncompress the patch installation executable ("emergency5_update_1_2_1.exe"). You can use 7-zip (http://www.7-zip.org) or any other program that has the same capabilities. 2. Inside the newly extracted directory, you should see three more directories. For the sake of clarity, we will call the directories as follows: "_゚", or the first directory, shall be referred to as "Dir1""_ユ", or the second directory, shall be referred to as "Dir2""_レ", or the third directory, shall be referred to as "Dir3"3. Enter "Dir1" and copy the "bin" and "data" directories. Paste them directly in the "C:\Program Files (x86)\Emergency 5\" directory (or wherever you installed Em5). Replace any files when requested. 4. Enter "Dir2". You should see a file named "content.7z". Extract the file into it's own directory. Enter the newly extracted directory. 5. Copy the "cache", "bin", and "manual" directories. Paste them directly into the "C:\Program Files (x86)\Emergency 5\" directory (or wherever you installed Em5). Replace any files when requested. 6. Ignore "Dir3". The files inside this directory are for the installer itself. Let me know if it works or if you run into any errors. I'll do my best to help as I can, but keep in mind I have not tested it (and nor can I)! Edit My apologies for the double-post! I had intended to add this post as an edit to my previous post, but forgot until after I'd hit the post button.
  23. Just to clear any potential confusion, I don't work with or for STE. I just reposted their patch changelog information from Steam. That aside, I'll take a look at the retail patch myself to see if I can figure it out. I have the Steam version, which is why I haven't personally bothered with the retail patches.
  24. Yes, 1.2 and 1.2.1 are two different patches. My post above has the changelog information for patch 1.2.1.
  25. A changelog for patch 1.2.1 was posted on Steam: Changes in version 1.2.1:· Forcing recognition of graphics acceleration on systems with Nvidia Optimus technology· Crash fix when fireman frees persons from gas station· Crash fix in multiplay lobby password entry· Fix for objects getting invisible during or after a building fire You can view it here: http://steamcommunity.com/games/328140/announcements/detail/172590889610052000
×
×
  • Create New...