Jump to content

jonwil

Staff Moderators
  • Posts

    1,355
  • Joined

  • Last visited

  • Days Won

    25
  • Donations

    0.00 USD 

Posts posted by jonwil

  1. I looked at the posted crashdump and whats happening is that the level loading code is trying to load a sound object that exists in the level. This sound object then looks for a sound file named "frank_klepacki_-_no_mercy_remix.mp3" (without the quotes) and either can't find the file or is unable to load it properly.

     

  2. Right now what we have is a reverse engineered clone of the pathfind generation that is (at least assuming there are no bugs left) producing valid correct usable output that matches the output of the original Westwood code in all the places that matter. And we have the same thing for the vis generation but its full of bugs that we are still in the process of fixing and is 100% not usable as of right now (to the point where using it guaranteed to produce bad output assuming it doesn't crash first).

    Note that pathfinding in Mammoth can't be canceled in the way it can with Leveledit so you will need enough pathfind blocking objects to ensure it is able to complete without running out of memory.

    We haven't really made any improvements to the pathfinding or vis generation yet (well there is one improvement in that if you proxy in a ladder transition object, it will now get proper action portals and bots will use that ladder). What happens in terms of improvements to that stuff will depend on what Neijwiert (the genius who did most of the work around pathfinding) ends up implementing.

    As for a UI that can edit the sky colors, that's not as easy as it sounds unfortunately. Maybe in the future I will look into it but right now the priority is to get all the things done that need to be done before we can completly drop LevelEdit for good.


    In terms of dependencies, what you need to do is to open Mammoth (assuming the version you are using is new enough) then open your level and choose "edit-include files". Anything you add to the list in there will be included in the mix file automatically when you use "export to mix" or "run game" or whatever). The list itself is stored in the .lvl file.

  3. I just added a feature to Mammoth so it will read these per-map sky settings. The old Westwood editor is going away in the near future since Mammoth is nearly feature complete (the main remaining thing on the to-do list is fixing all the bugs in our reverse engineered clone of the vis generation algorithm) and definitely couldn't have this stuff added in any case.

    When you change the ini you will just need to reload the map and it will read your changed sky colors.

    As for the dependencies, Mammoth makes it trivial to add the ini file as a dependency of the map (that will get automatically exported into the map mix file). The dependency information is then stored in the .lvl file and travels with that.

  4. A good place to start would be to run Windows Update and install anything it offers to install. Also update your GPU drivers (this https://downloadcenter.intel.com/download/18223/Intel-Graphics-Media-Accelerator-Driver-for-Windows-7-exe- looks like the latest version for your GPU as far as I can tell)

    Its entirely possible though that an Intel GMA 3100 GPU with only 256MB of video memory simply doesn't have the grunt to run APB (it wasn't exactly good even when it was released)

     

  5. The new level editor (Mammoth) does NOT support Renegade and scripts 4.x.

    Its only for scripts 5.0 (which is what APB/AR/TSR/BFD are using).

    I dont see any reason why the new MAX tools wouldn't be usable for Renegade and scripts 4.x, nothing has changed in terms of the w3d file format.

     

     

  6. The page file doesn't work like that, there is no way the page file could be the cause of his problems.

    An error with the BIOS could cause it though.

    Nothing in the new crashdump that looks useful in tracking down the issue (although its strange that he said he installed everything Windows Update offered to install yet he doesn't have the same versions of key Windows DLLs that I have when we both have the same version of Windows and I have every update Windows Update offered to install as well)

    And how can he have a "custom built PC" and also have a Dell Optiplex?

     

  7. I would suggest that you run Windows Update and install all the updates for Windows and also update to the latest NVIDIA drivers. If that still doesn't make your problems go away, I would suspect a possible hardware fault (the symptoms you describe sound like what happened to me when my previous graphics card failed and I had to buy a new one)

    Also can you look for the windows folder (probably c:\windows) then go to system32 and look for ntdll.dll. Select it and press alt-enter. Then click on "details" and tell me what it says under "file version".

     

  8. Unfortunately, due to the departure of Saberhawk (who took all our infrastructure with him) we no longer have the necessary debug information to debug those crashdumps. We will at some point of course push a new game build with new scripts that we can actually debug but those particular crashdumps can never be properly debugged due to the loss of the debug information required.

     

  9. Forget the Visual C++ runtime, my analysis of the crashdumps suggests it looks fine.

    The best thing to try is to go to the launcher, click the little icon above where it says "release" and then click the "repair" button. That will make sure your installation is correct with no corrupt or missing files.

     

×
×
  • Create New...