Jump to content
Official BF Editor Forums

clivewil

Members
  • Content count

    922
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About clivewil

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    http://
  • ICQ
    8094584

Profile Information

  • Gender
    Male
  • Location
    Perth, Western Australia
  • Interests
    3d gaming, music

Recent Profile Visitors

14,579 profile views
  1. clivewil

    Strange Ai bug, how to fix ?

    i just downloaded that map down from fileplanet to take a look, and it has no navmesh or ai. what is yours using, did you make your own?
  2. clivewil

    Somes Questions ! Mapping/modding

    combat zone? i'm assuming you mean combat area? the combat area is the border around the playable area on your map, if you go outside this you'll hear the 'deserters will be shot' warning and see the countdown. there can be separate combat areas for soldiers, vehicles and aircraft or you can just use a single one for everything if 'usedByPathfinding' is checked for a combat area, it will also define the borders of a new navmesh that you create (so normally the soldier combat area is used for this, because it's the smallest) StrategicAreas (SAs) are used by the a.i. to determine whether they are inside the ControlPoints (CPs) or not - each one will have an ID that matches its CP's ID, and it will also have a 'temperature' to determine how hot (i.e. important) it is to the bots, e.g. if CP1/SA1 has a temp of 50 and CP2/SA2 has a temp of 200, the bots will be more likely to pick CP2 as their destination. note this temp is only a small part of the bot's strategy, any vehicles at the CPs also have their own temps which are all added together to get the total combined temp for the CP you didn't mention OrderPositions, so i'd better explain them too: each CP/SA has an OrderPosition of infantry, and another for vehicles. these determine exactly where a bot will go to try and capture the CP, so the infantry OP *must* always be inside the CP radius - you can be a little tricky with these; i would often place them behind an object or inside a building so the bot capturing the CP had a some cover instead of standing out in the open like a lemon vehicle OPs work in two ways: if it's *inside* the CP radius, the bot will drive up to OP and sit there until the flag is capped. BUT if it's *outside* the CP radius, he will drive up to it and then exit the vehicle, and proceed on foot to the Infantry OP and cap the flag from there. for the carrier in AIX2 i made a custom ramp and stairs for the carrier that make the entire path from the sea to the deck walkable without needing ladders, which bots can't use. if i remember correctly they are called Carrier_Ramp and Carrier_Stairs_inc and are found in AIX2's staticObjects/misc folder. you use them by putting them in your map and aligning them to the carrier before you generate your navmesh OrderPositions for bots on the carrier are a special case: if you try to set them, the OP will snap to the terrain, which is useless. to give them valid positions, i would create 2 temporary spawnpoints e.g. DeleteMe_Infantry and DeleteMe_Vehicle - the infantry one gets put on the carrier deck inside the CP radius (or wherever your CP is in the carrier) - the vehicle one i usually put just outside the carrier's rear hangar, level with the surface of the sea. (put it inside the hangar and it can get congested; put it too far outside the hangar and the bots take too long to swim inside to the ramp) once you have created these spawns and saved the map, you can copypaste their position coords into the OP coords, then delete the spawns afterwards. you can tell if they are correctly placed because they will show up as green circles (vehicle circle is slightly larger than the infantry circle) - if the circles are red, it means their position is not valid. NOTE that this is also true for spawnpoints and vehicle spawners - any showing a green disc are in a valid position for the bots; if they have a red disc they must either be moved or marked as 'human only' so the bots don't try to use them IMPORTANT - you must load your navmesh in the editor in order to see the red and green circles and discs - otherwise they'll all show up as red. in the text boxes select: AiPathfinding > LoadGTSData > click green button in the Render menu select: Render > Ai > Toggle draw ai and then: Render > Ai > Toggle draw infantry navmesh OR Render > Ai > Toggle draw vehicle navmesh ...your navmeshes should show as having green land, yellow shallow water, and blue deep water. i'll let someone else step in and explain the other stuff you asked about. good luck and have fun ----> oh and one more thing - if you render your reflection maps and you see a line of white letters/numbers showing in your water and glass, disable the SP editor, quit and restart the main editor and then render them again.
  3. clivewil

    need some (a lot) help

    i'm not a mapper as such but i have made a couple, and modified many... what is the folder/content heirarchy you have set up for the mod? for my own stuff i found it was MUCH simpler to have a separate version of my mod purely just for mapping + modelling this mod contains all of the vanilla BF2 mod plus all of my own mod's files, all extracted* * that is, no zips. e.g. all of the files from MyMod_client.zip and MyMod_server.zip would be unzipped into a folder called MyMod, keeping any subfolders intact. the idea is that the game engine can find any file it requires right there in front of it's face to avoid any errors caused by 'cannot find file nnn' any maps or models i'd completed got copied over to a separate playing/testing mod, for two main reasons: the playing/testing mod didn't need to be quite so bloated as the mapping/modelling mod. the editor can and WILL frequently bork the scripts for your exports. it's not so much a problem for mappers, but for new vehicle exports etc. the editor would frequently add unwanted code, or remove wanted code, or other skullduggery. DICE said that they used this method themselves, which is why the editor never got refined any more than the final version - they already had this technique as a workaround. bear in mind that the editor is v1.3 so you'll need to take into account any differences that occurred between v1.3 and v1.5 - for new models there were a few things that needed adjusting, i don't know if maps had any similar pitfalls. if this mod is purely for your own use, don't bother packing your map - they run perfectly well unpacked (i.e. no server/client zips, just plain files) and it's much easier to edit stuff on the fly without having to unzip-rezip every damn time you make a small change. an unpacked map is typically about 150mb compared to 50mb for a packed map, but this is 2019 and we aren't as scared of filling up our hard discs as we were back in 2005 when BF2 was new. good luck.
  4. dammit, when reading your title i thought it meant EA had already planned to release it - not 'will they ever release it'
  5. clivewil

    Welcome Back Bf2Editor!

    yay!
  6. clivewil

    Navmesh Problem

    sounds like Python might not be properly installed or associated? and don't just run the bat file; open a cmd window, cd to the correct folder and run the bat from in there. the window shouldn't close until you do it manually.
  7. aha good old sagethumbs, i use that myself because it makes photoshop .psd's show thumbs too. it's a great little add-on.
  8. you might be better off looking at the ai for the soldiers rather than for the grenade - perhaps you could try changing their behaviour in AIBehaviours.ai, e.g. from memory there's a 'take cover' behaviour that might stop them running if its value was lowered enough, of course i might be wrong but it's worth a look
  9. clivewil

    Lod1 Heirarchy For Statics

    only lod0 needs the set of col meshes, you can delete nonvis_ and anything downwind of it from lod1 <br> <br> in most cases you'd use the same shader because the material would be the same and the UV's would be similar too, although less complex
  10. clivewil

    P-51d Mustang And Bf-109e Emil

    nope. doesn't work for me. might be a script problem or it doesn't like my version of firefox. no option to use bold, underscore, italic, font size - i get none of that stuff, i have to enter the tags manually from memory. preferred the old board setup.
  11. clivewil

    P-51d Mustang And Bf-109e Emil

    hmm not for me it didn't, i had to use < br > or else it all shrunk into one chunk 'more reply options' just shows me a preview of my reply, it doesn't give me any options and what does "this is project reality jet" mean, is he saying i stole it, or that PR did
  12. clivewil

    P-51d Mustang And Bf-109e Emil

    cheers! how's the B-29 stick bombing in the first clip, i knew they had a large load but wow - massive hurt underneath that lot. i gave some thought to your baka/ohka last week - it has a very simple cockpit which is a plus seeing as i hate making cockpits. you'd have to stretch reality with the landing gear though, e.g. keep the skid but have invisible wheels so it could land and steer on the ground, or else it wouldn't be much use -------- we need some formatting tools in here, the new forum doesn't recognise line breaks. it makes all my text turn into a single paragraph -------
  13. clivewil

    Updated Ipb Software

    i'm glad the url loop got fixed. one question: where's the formatting tools gone to, e.g. quote, bold, font colour, link, image, codebox etc? i can't see them anywhere...
  14. clivewil

    Updated Ipb Software

    all ok so far, apart from the initial scare of thinking i'd come to the wrong site
  15. clivewil

    Corona's Shaders

    interesting. thanks Corona
×