Jump to content

lordfeff

Members
  • Posts

    24
  • Joined

  • Last visited

Reputation

10 Good

Converted

  • Biography
    Geek/Nerd Ive been playing games since my Commador64 .. Yes games were on a cassette tape and cartrage. I like anime and games and usually I talk about one or the other.
  • Location
    New York
  • Interests
    Games Electronics Anime Software
  • Occupation
    Jr Engineer
  1. Hi all. If this bug annoys you there is a work around. I will supply the work around for the Industrial Light Scout 1 Map where you are facing the wrong way in the upper Left Corner of the map. I'll try my best to make this fix easy to follow. *Click signifies Left-Click, Right-Click is always specified. 1)Navigate To Your Xenonaughts Base Folder (whereever that may be... in desura its (programfiles(x86)/desura/commen/xenonaughts) on win 7 2) open the program there called GCLevelEditor 3) Click load button on window that appears 4) Select Industrial from the Tileset Drop Down Box. 5) Click Industrial_LightScout1 and then Click the OK button. 6) Look to the right of the window. You will see your on the Main Layer Tab. Click Spawn/Target layers 7) In the box below this tab you just clicked you should see an entry CHECKED for airplane.human.chinook - SE. Click This Entry. 8) On the map you will see human.chinook box slightly brighter then the rest. RIGHT click the bright yellow box labeled human.chinook to remove it. 9) Verify that airplane.human.chinook - SE is now NOT checked 10) Click On The Entry that says airplane.human.chinook - SW 11) Click on the giant green Square. If the square is not centered into the green area click and hold the left mouse button down on the human.chinook yellow square and drag it so it lines up perfectly in the green square. 12) Verify airplane.human.chinook - SW is now CHECKED. 13) Click Save Button. By default the window that appears should say Map name - industrial_lightscout1. Click OK. 14) Click Yes to the prompt to overwrite it. 15) Close the editor and enjoy the fix. Comment: (The Chinook Renders out toward the East. It is not perfect but at least your setup is not backwards! Pics Attached) This trick will work on other maps as well where you might find this setup. I have only just started so industrial_lightscout1 is the only map I have seen this happen in as of yet. I have seen aliens spawn INSIDE the hull of the ship on some maps. I suspect this may be related. If you can identify the map you can use this method on THIER ship and change its direction. This will cause them to spawn correctly within the UFO. Its important to know if the UFO is crashed or landed as I believe there are 2 separate spawns depending on the condition of the alien craft. Trial and error I say. Happy Gaming!
  2. I am aware the devs know of this bug and probably already have the fix in the works but I thought to supply this added debug information in case it is useful. Dump Summary ------------ Dump File: XenonautsCrashDump.dmp : C:\downloads\Build_V13.2\XenonautsCrashDump.dmp Last Write Time: 8/19/2012 2:55:13 PM Process Name: Xenonauts.exe : C:\downloads\Build_V13.2\Build V13\Xenonauts.exe Process Architecture: x86 Exception Code: 0xC0000005 Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access. Heap Information: Not Present System Information ------------------ OS Version: 6.1.7600 CLR Version(s): Modules ------- Module Name Module Path Module Version ----------- ----------- -------------- Xenonauts.exe C:\downloads\Build_V13.2\Build V13\Xenonauts.exe 0.0.0.0 ntdll.dll C:\Windows\SysWOW64\ntdll.dll 6.1.7600.16385 kernel32.dll C:\Windows\SysWOW64\kernel32.dll 6.1.7600.16385 KERNELBASE.dll C:\Windows\SysWOW64\KERNELBASE.dll 6.1.7600.16385 dsound.dll C:\Windows\System32\dsound.dll 6.1.7600.16385 msvcrt.dll C:\Windows\SysWOW64\msvcrt.dll 7.0.7600.16385 user32.dll C:\Windows\SysWOW64\user32.dll 6.1.7600.16385 gdi32.dll C:\Windows\SysWOW64\gdi32.dll 6.1.7600.16385 lpk.dll C:\Windows\SysWOW64\lpk.dll 6.1.7600.16385 usp10.dll C:\Windows\SysWOW64\usp10.dll 1.626.7600.16385 advapi32.dll C:\Windows\SysWOW64\advapi32.dll 6.1.7600.16385 sechost.dll C:\Windows\SysWOW64\sechost.dll 6.1.7600.16385 rpcrt4.dll C:\Windows\SysWOW64\rpcrt4.dll 6.1.7600.16385 sspicli.dll C:\Windows\SysWOW64\sspicli.dll 6.1.7600.16385 CRYPTBASE.dll C:\Windows\SysWOW64\CRYPTBASE.dll 6.1.7600.16385 ole32.dll C:\Windows\SysWOW64\ole32.dll 6.1.7600.16385 winmm.dll C:\Windows\System32\winmm.dll 6.1.7600.16385 powrprof.dll C:\Windows\System32\powrprof.dll 6.1.7600.16385 setupapi.dll C:\Windows\SysWOW64\setupapi.dll 6.1.7600.16385 cfgmgr32.dll C:\Windows\SysWOW64\cfgmgr32.dll 6.1.7600.16385 oleaut32.dll C:\Windows\SysWOW64\oleaut32.dll 6.1.7600.16385 devobj.dll C:\Windows\SysWOW64\devobj.dll 6.1.7600.16385 IPHLPAPI.DLL C:\Windows\System32\IPHLPAPI.DLL 6.1.7600.16385 nsi.dll C:\Windows\SysWOW64\nsi.dll 6.1.7600.16385 winnsi.dll C:\Windows\System32\winnsi.dll 6.1.7600.16385 wininet.dll C:\Windows\SysWOW64\wininet.dll 8.0.7600.16385 shlwapi.dll C:\Windows\SysWOW64\shlwapi.dll 6.1.7600.16385 normaliz.dll C:\Windows\SysWOW64\normaliz.dll 6.1.7600.16385 urlmon.dll C:\Windows\SysWOW64\urlmon.dll 8.0.7600.16385 crypt32.dll C:\Windows\SysWOW64\crypt32.dll 6.1.7600.16385 msasn1.dll C:\Windows\SysWOW64\msasn1.dll 6.1.7600.16385 iertutil.dll C:\Windows\SysWOW64\iertutil.dll 8.0.7600.16385 version.dll C:\Windows\System32\version.dll 6.1.7600.16385 dbghelp.dll C:\Windows\System32\dbghelp.dll 6.1.7600.16385 shell32.dll C:\Windows\SysWOW64\shell32.dll 6.1.7600.16385 SDL.dll C:\downloads\Build_V13.2\Build V13\SDL.dll 0.0.0.0 comctl32.dll C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7600.16385_none_ebf82fc36c758ad5\comctl32.dll 5.82.7600.16385 winspool.drv C:\Windows\System32\winspool.drv 6.1.7600.16385 comdlg32.dll C:\Windows\SysWOW64\comdlg32.dll 6.1.7600.16385 imm32.dll C:\Windows\System32\imm32.dll 6.1.7600.16385 msctf.dll C:\Windows\SysWOW64\msctf.dll 6.1.7600.16385 uxtheme.dll C:\Windows\System32\uxtheme.dll 6.1.7600.16385 profapi.dll C:\Windows\System32\profapi.dll 6.1.7600.16385 dhcpcsvc.dll C:\Windows\System32\dhcpcsvc.dll 6.1.7600.16385 ws2_32.dll C:\Windows\SysWOW64\ws2_32.dll 6.1.7600.16385 clbcatq.dll C:\Windows\SysWOW64\clbcatq.dll 2001.12.8530.16385 MMDevAPI.dll C:\Windows\System32\MMDevAPI.dll 6.1.7600.16385 propsys.dll C:\Windows\System32\propsys.dll 7.0.7600.16385 AudioSes.dll C:\Windows\System32\AudioSes.dll 6.1.7600.16385 dwmapi.dll C:\Windows\System32\dwmapi.dll 6.1.7600.16385 d3d9.dll C:\Windows\System32\d3d9.dll 6.1.7600.16385 d3d8thk.dll C:\Windows\System32\d3d8thk.dll 6.1.7600.16385 nvd3dum.dll C:\Windows\System32\nvd3dum.dll 8.17.13.142 psapi.dll C:\Windows\SysWOW64\psapi.dll 6.1.7600.16385 comctl32.dll C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\comctl32.dll 6.10.7600.16385 avrt.dll C:\Windows\System32\avrt.dll 6.1.7600.16385 Assembly Break Line: 014558E3 mov edx,dword ptr [esi+1Ch] Hope that was helpful
  3. Anwsers: If your talking about Desura being the problem then : Taken from this very thread. Reading is fundamental.
  4. Interesting. I'll look into this when I am home and can play again. I'll try messing with the sound files. Also if you hit L during a bad load you get 7+ error boxes. It's not a Pathing issue as I realized you can't fire your guns during a bad combat load either. I've tried everything map wise to no aval. The dump states a c000005 error which means the computer application I can't tinker with xenonauts.exe is either trying to divide by 0 or allocate data to memory that does not exist maybe null data I don't know for sure. I do light visual studio programming so I know a little but I'm no expert coder or anything. Most Lilkely well need another hot fix.
  5. Sorry if you saw my post. I did a work around and got through 17 ground missions without crashing. I tried to duplicate this effect afterwards however I was not successful as the game crashed once I restarted the game and loaded my save. Seems this one is gonna be tough but I will keep trying to try to get a work around that makes it go away completely. In case you were wondering I removed tilerender.xml and got it to crash less often and you are welcome to try it out. It does have some rendering side effects so you should back it up so you can replace it. Once again sorry if I got anyones hopes up so soon for a permafix.
  6. The manual download is up so you don't need desura. As for the other gentlemens question there is a game manual posted for this game although I am not sure if 11 and 12 are bound yet. I click On there mini stat bars to select them for now.
  7. It happens when you "CLICK" on a unit be it soldier or tank. You can avoid the crash by using the hot keys to select, well at least for me that is the case. I can also tell you that all tanks are poison so you should not use them in 13.2. I have changed a rocket tank to an MG tank which actually kicked major butt however once I reached ground mission 4 i got the destroyed tank model on load and I "Clicked" on it like a fool and then came the infamous CTD. I am currently working on playing through VMware player with one of my alternate OS's I have from my old decommissioned computers. The reason is that I do not want to save as I believe loading a save game is just as poisonous as using the tanks. If your wondering VMware is software that allows you to run another OS on your computer in a window(sorta like remote desktop works) as when you close it the state of the computer is suspended and can be resumed from any point
  8. Crash to Desktop After Ground Battle Loads Easy Work Around for 13.2: I have not encountered enough ground battles to confirm this 100% but the last couple of times I came to realize that if you do not CLICK ON the units the game will not crash. You will not be able to move your units though after you hit control + 1 for your tank or whatever number key selects your closest guy to the ramp. When you try to move off the ship you will see that you are stuck but the game will not crash if you do not click on any of your units. At this point simply press the letter "V" and poof the ground mission ends and off you go on your merry way. Hope this helps and I'll let you know if this method continues to work as I am playing. Okay so here is my final run down. This trick works however the downfall is that it appears that every single ground battle afterwards will be bugged. I can no longer do any ground battles without either clicking on a unit and crashing the game or pressing v to skip the ground battle entirely. I also noticed that I could not re-assign my tank and i tried selling my Chinook and using nothing but troops but alas still got the bug. Seems nothing short of modifying game files or waiting for the next patch/hot fix will fix this.
  9. Yup tried that at different heal settings 5, 10 Etc... I thought that was represented by the light grey bar but if what you say is the case it is possible as my goal was almost full hp and I only noticed after wasting 3 of my teammates turns that it was not working. Thanks for the heads up tho I'll keep an eye out for this specifically next time I'm playing tonight.
  10. So I have experienced this bug as well when the map loads the game would crash. However by a fluke where I believed it should of crashed it did not! Guess what I am missing?! THE RAMP TO GET OFF OF THE SHIP! Maybe that's a hint to this bug? Game didn't crash but obviously I could not get off the ship either. I started using hot keys instead of clicking on the tank which may be an odd reason why it did not crash although this is just me trying something else. Well after posting this i accidentally clicked on a soldier instead of hot keying... Game crashed. Hmm very interesting right?
  11. I tried to use my medpack from all soldiers around her and even her own medpack(which i realized she can't heal herself) I tried using 5/10/15/20 hp heal methods. Nothing worked she is stuck at 29/57hp. I attached a pic of her hit point bar so you can see and maybe even tell me if I am putting my foot in my mouth on this one. P.S. The damage was caused by friendly fire.
  12. I also thought to share that it took me 2 grenades, 2 rifle rounds that hit,1 round from my Heavy MG,a smoke grenade, a tank missile launch(2 actually but my second missed completely), and finally a sniper round to take this alien down. He did not take any direct hits from the explosive shots (grenades, missiles) but even still my god he was strong lol. This was why my guys were posted up where they are in the previous post above. Oh and don't throw smoke grenade till last cause that made it harder for my sniper to hit. Luckily he hit his mark through this nuclear cloud of smoke =P
  13. I came across this pathing bug. It seems I am able to move my soldier onto another soldier in this location. I don't believe this is suppose to be possible. Attached Screen Shots.
  14. Yes the game states "ITEMS ORDERED TO [YOUR BASE NAME] BASE HAS BEEN ARRIVED." It Should Say "ITEMS ORDERED TO [YOUR BASE NAME] BASE HAVE ARRIVED." Sorry I missed your response here but yea I agree maybe just re-word it to say "YOUR ORDER AT [YOUR BASE NAME] BASE HAS ARRIVED" Should be a simple fix and close to the current message but I do like the courier plane idea too although I would like mine to be the A330 MRTT by Airbus. It has a 45ton cargo hold and reaches speeds up to 860km/h traveling up to 14,800km. I think it can do the job
  15. Your right I suppose then it should simply say: This mode forces the player to live with their mistakes, providing more tension. [The following text that appears afterwards is fine.]
×
×
  • Create New...