Jump to content
Battlefront is now Slitherine ×

rune

Members
  • Posts

    3,769
  • Joined

  • Last visited

Everything posted by rune

  1. Sit down bauhaus , Joebob , I will claim this nipper of backsides.....what? Yes...yes...buns...but I ALREADY told him to sit down. Oh where was I? Oh yes, I claim this yipper of buns for House Rune with all right and previledges, etc. etc. NG Cavscout , I make this Pommie your chew toy. [pom me n. 1. An Australian who just hasn't made the trip yet] I want him trained correctly, and with MUCH pain. Use the *BOOT* and often. Start him with a rune scenario...might as well start him off right. So let it be written, so let it be done. Rune
  2. It would also mean the game would be unplayable. The hardware could nto support a map of that size...it is pushing it at 4 km. The design decision was it was too difficult to code to use the map with burning vehicles, destroyed buildings, etc that would happen during a battle. You can use the same map, but the building you destroyed may magically be back. Remember, you have AI plans, things would change and how could you let the plan know? How would you import an entire map? Bottom line, there was no easy way to code this, so it is not in. In the future who knows, but I would not bet on it. Rune
  3. Nope, it is both, terrain and amount of units. As I said, make sure you test anything you create...I cannot say that enough. Rune
  4. Guys, Don't go overboard. Remember, the maps are more detailed then CMX1. You may want a big map, but add a 4km by 4km forest and the map alone will require a crey computer to process. Remember, this game is also setup to play real time. Add a division of troops to a map, and I can already hear players requesting the head of the designer. A company is the perfect size to play without being over-whelmed. So, yes, you can make a 4km by 4km map, but you better test the heck out of it to see what fps you get. Not everyone has a 4 core processor with 8 video cards in sli mode. Remember, you ARE chatting with the big scenario master here...and if I am warning you...test it completely first. Rune
  5. Indirectly... You set a win go to scenario xyz, lose go to scenario abc. In the scenario, you can set those parameters, so it will determine winner/loser and which scenario then to go to. Actually some of the scenarios we created may not be seen for some time. Depends if you win or lose. Rune
  6. Correct... the max size is 4km in any direction. So east-west max is 4 km. Ditto with north-South. Rune
  7. Wicky, if you can post the third section on thursday, it would be appreciated. Designer tip: When you merge buildings together, you should remove the walls inbetween the buildings to give more of a flow to tropps moving inside [remember internal walls and stairs and doors are NOT shown] UNLESS you want a load bearing wall in between. Generally unless a large flat warehouse type building, I remove the walls if the two building are the same height, and leave them is you put a 2 story building next to an 8 story building as part of the same building. Rune
  8. No, am busy working on a scenario for something. Rune
  9. Yep, and trust me, in some of my scenario, i have some nightmarish thin allyways. Infantry can go, but not he vehicles. Rune
  10. No redwolf it was not straight lies and I would be careful on saying that. The table I filled out and sent to 1C in their format are different then what is in the encylopedia, and as in this thread, I posted that 1C did say the encylopedia is factored in a different way from the tables. I do NOT know if the numbers I sent them are hard coded in, and then if modded, these are used. I forwarded the information to Martin, but I have YET to get anyone to send me something I can send 1C. The figures I researched and sent are within 1mm of Bird's book, and people like John Sale reviewed them. I even sent copies of the spreadsheets to people here online to review. Don't cross the line and call me a liar. I deal very much straight up. is there a bug, or something else hidden under the Code? I can't answer..I didn't code it. Someone give me something to go to 1C with, and I will. thewood, yes, someone from 1C did indeed say that. Rune
  11. Oh yeah, this is NOT the manual, but an additional guide on how to make a scenario. Done by the people already mentioned to give the scenario designers a heads up on how to create under the new CM. It is a draft, and the final version is being corrected, so there are some typos, and some out-dated screenshots, but you will get the general idea. Rune
  12. Yep, and finally remember everyone this is a draft, so there are some errors. the final version is being tweaked as I type, and will have more up to date screenshots and will be edited better. However, at least this gives you an idea of how the scenario design will go. Will have the second section out up tomorrow. Wicky, thanks for doing this. Please post Section 2 tomorrow for everyone to look at. Rune
  13. I do but you won't. PDF compressed is 7 meg, so not so bad. Will send it to you now. Let me know when you get it. Rune
  14. Wicky, If you can break up the pdf into various files, then we can give it a go. Post a section every few days, we can work it out. Can you break up the pdf, or I have it in word format. Rune
  15. I haven't been able to reach the mad one while home. I tried google documents, but it is too big. Anyone have a way to view word documents or pdfs online? I tried google documents but the file with screenshots is WAY too big. Rune
  16. Sorry guys, the madone has been busy and I havent been able to reach him yet. Still hoping to get the first part up soon with screenshots...won't do the text alone, it won't make much sense without screenshots. Rune
  17. No problem, however have to wait for the mad one to wake up before posting the next section. Let a sleeping madmatt lie as the saying goes. Hang in there guys. Rune
  18. Hang on, first section will be posted, but have to wait till Matt gets up, trying to come up with the best way to do screenshots. Tons of them in the next few sections. ang in there, sometime today. n George made this at my request to help other scenario designers during hte beta process. I think he did a hell of a job. Kudos go to him and Mace and others for helping him edit the doc. Rune
  19. Combat Mission: Strike Force A Guide To Using The Scenario Editor Introduction This manual will in a series of easy to follow steps take you, the designer, through the process in creating a custom built scenario for CMSF. Our custom built scenario will be set in a large built-up fictional city landscape. In this scenario a US Stryker platoon (commanded by a human player), operating on Intel gathered from a variety of sources has been tipped off that a Syrian ‘Irregular’ unit (commanded by the AI), will be advancing to recapture a Mosque in the US held western part of the town. The US commander has set-up a classic ‘L’ shaped ambush, which it is hoped the advancing enemy unit will walk into. In the process of building this scenario you will find out how to build a 3D map, create set-up zones, purchase and deploy combat units, assign unit objectives, and create a series of AI plans that the AI can use to structure it’s attack. The manual is in four sections. Section 1 Orientation – covers what is in the scenario editor and a brief outline of what it does. Section 2 Creating the Map – using the map editor and creating the map your pixel soldiers will fight on. Section 3 Purchasing and deploying Units – how to purchase, edit and deploy on the map your combat teams. Section 4 Setting the mission and objectives – how to set what are the victory conditions for your scenario. Section 5 Creating AI Plans – how to create a cunning and variable plan for the AI commander to follow. Section 6 Finishing Touches – creating tactical maps, inserting the mission orders for each side and general tidying the scenario up sort of stuff.
  20. Yes, there is one red vs red scenario. No Blue vs Blue. Rune
  21. I am running hte game here under Vista 32 bit and Vista 64 bit. There are still bugs in the drivers for 64bit. 1. Shadows have to be turned off. 2. A write setting has to be turned off with the 8800 card, which makes the game run a little slower. NOTE: NEither of these conditions exist with the 32 bit version of Vista. I am currently running the 160.04 version of the Nvidia driver. Rune
  22. Windows 2000 is NOT a supported OS. The game is using opengl, not sure how support for opengl is in Windows 2000. I do not believe it was tested at all with Windows 2000. Rune
  23. OK, I emailed Martin to get an answer on this, and hopefully he will hear from 1c soon. Go ahead and still let me know, but I will see if the value in the .ini are what are used in game. I know the tables I created are different then the encyclopedia and ini files. Rune
  24. Guys, I KNOW I sent them the correct numbers, and in the thread posted above, I see from the developers: SoaN Moderator Member # 23565 posted May 08, 2007 01:34 -------------------------------------------------------------------------------- All penetration values are counted in one system. All penetration angles are 0 degrees when it’s counted. You may have hit on a bug if you are seeing something. Do some more testing and forward anything you find to me, and I will send it to them immediately. Oh and Ryan, before going off on a giant conspiracy thread, a simple question here goes a long way. Rune
×
×
  • Create New...