shinRaiden

There is two communities because public VBS is just now kicking off. It remains to be seen how the communities will co-exist, and if there will be any leaching. I presume though, that there will be a more mature audience with VBS from the price tag and from the target audience. If you want toys, they'll be in OFP as well. If you want tools, chances are you'll have to play ball. - on topic - Coalescent has hints about several sizable Homeland Security themed projects in the works, and all the help on VBS I'm sure will work its way back into OFP. In a way, this is an opportunity to help make the product the very best. Then again, it only has itself to top.

I'm not totally sure on this, but iirc, the russian port is a significant port of all the strings and stuff by a russian translation firm, and I doubt that all the material would be available only in a patch. You most likely need to purchase the full translated copy in russian, and then patch it up.

Before a good solution like that can take off, there needs to be more coordination and standardization between mods. As a 56k'r student in a remote rural area, I don't mind having to plan a trip to find a free hotspot to dnld an addon. But when I have to download the entire pack again to pick up additional independent new models, or cpp changes, I'm probably not going to. And if there is a track record of that kind of project management, I'm probably not going to dnld their stuff at all. You can split the configs, shared data, and specific models into separete PBO's. Plus the reduced download sizes could reduce strain on hosting as well. Any way, OFP needs dynamic ingame loading/unloading of addons. Maybe an option on the front screen, that pops up a list of addons you've "checked in" to a xml file with an external app like the preferences app. In game, the xml config would get parsed and a sanity check to make sure that file is there, and to flag dependancies. If you have broadband, you could check an option that would hit a master site, or sync'd replica, to see if there is a new version of any or all addons. Additionally, you would want to make it so that you could call that dialog from the missions, mp, and editor sections as well.

One option is to fiddle with the landgrid setting. The standard is 50m, but you can crank it up above that too. While this may make for jaggier islands on the same view detail settings, it's one step to giving the OFP pilots more wing room without running into the vibration problem. The problem with that though is that all 3 wrp editors currently available presume that you are using a landgrid setting of 50m, and don't have offsets to correct the placement of objects. This is because objects are placed independently with absolute values, and the only adjust vertically in certain cases like bridges.

I too have the 'no sound except a low hum' issue. Engine noise was almost non-existant as well, until I turned off ECP-DR. I'll wait until the re-ship and see what happens. I too have an nforce2 soundstorm. Bigger issue that I haven't see posted is when I'm in 'sights', first, or second views as gunner, the suspension goes all wacko, with the whole body rocking front to back. Switching to third-view and back cancels it, until I move the turret again. Here's an idea from left-field... is it possible to make certain components, such as the fording kit and stretcher seperate objects that can be proxied in? That could cover the major difference between the USMC and ARMY variants. Thanks for your work. They look great. Thanks.

Certain widgets like the Immersion Foundation Classes (IFC22.DLL) and such DirectX/DirectInput libraries are licensed components that would not be openable. Another good example is the quake2 sdk system. That's how half-life came to be anyway, and that is a wonderful way to learn how to code. In Quake2 dev, there was a couple mod groups exploring a similar plugin structure where the gamex86.dll could be split into a set of modular plugins. I don't think they got very far because of RL issues. Anyway, right now we're seeing some serious fragmentation of unique mod's using incompatible config.cpp's and such. My concern is that an open SDK could easily exacerbate that problem. Implenting a plugin system with an open API in OFP could be beneficial by allowing different developers to create targeted plugins, similar in fashion to how we currently add objects to root classes. While this may sound good in theory, considering the fights over to JAM or not, I expect that there would be as much avoidance of standards commonality with an open SDK, as there is without, which would negate the entire intent and purpose of the exercise. On the other hand, I'm not familar with the internal structure of the OFP engine and development of course, and I could justifiably presume that there is IP sensitivity in regards to physics and AI modeling and methods. The other difficulty is that to effectively explain why a component will not work would likely require an explanation of how that component works, which would involve function disclosure.

Something that just came to mind is how come turrets spin completely independent of the chassis? How about making the turret direction an offset of the vehicle, like helicopter mg's?

I'm not sure how or why it has taken me this long to click this theory together, but considering FullSpectrumWarrior, is there more VBS-OFPxbox connections than maybe we are anticipating? Economically, there is no IT overhead for xbox'ing. Just ship a crate of xbox's, and how hard is it to find a tv somewhere in the world? Anyway, my real question is is that keyboard layout available commercially? I didn't see any link in the webstore, and Ideazon doesn't have any listing either.

As for Boeing and Airbus, Boeing continually beat Airbus in sales despite the subsidies, until Boeing chose to self-destruct. Boeing is currently in the process of voluntarily shutting down commercial jet production. Why? Not because they were competative, but because they weren't interested. By closing operations, you kill head count and can write-off the expenses. That looks good on paper to the screwed-up analysts machines. Boeing instead is choosing to focus on government pork projects. However, the new management, which drove several aquired subsideries into the ground, has embarked on a path of corruption as bad as Enron and Worldcom. Fortunately, various people in congress have been alerted and they have been putting the brakes on as best they can. While I personally think that the subsidies != contracts, us vs. them is not a good arguement. Sadly, this problem is not unique to Boeing.

And what do you term to mean illeagal? The pro-abortion arguement is that Government has no compelling right to interfere in an inherent 'human' right to one's own body and body components. The problem is that there is no significant 'human rights' specified in the US constitution, rather a framework of legal rights granted or managed in regards to the determined citizenry. Current legal wranglings in the US are drawing on international laws and theoretical musings to determine the applicability of 'human rights'. In reading the majority opinion of Roe v. Wade, the court found that as science, philosophy, and such has no consensus on when 'life' begins in a physical, metaphysical, or legal circumstance, the court is also not qualified to make such a determination. Therefore, they ruled that the only significantly determinable factor was the mother, that that would carry the day. Now, to change this securely would require a constitutional amendment, similar to the amendments that corrected the initial injustice of legally defining blacks as property and not human, therefore not potential citizens, and extending full voting rights and responsibilites to women. However, this opens the entire case of legislating a 'human rights' amendment package. It would not be fair or competent to attempt to address these issues seperately, so they need to be lumped into one big package because of the common philosophical and scientific foundations: * Abortion * Gay marriage * Euthanasia If you attempt to split them up, you are not effectively addressing the fundamentals of the issues. The question before the people is "what is life, and who is entitled to it, and who is entitled to determine it?" Unfortunately, we don't have a serious quorum of representatives and senators who are capable of considering this. There is too much intrenched politicking and establishment to make waves to decide this one way or another. This results in the legally dangerous position of evangelicals throwing legislative barbs at the judiciary's darts, and the continuity, applicability, and respectability of the law goes right out the window. That said, this shouldn't even need to be an issue. As a democrat said yesterday in a debate, every (partial-birth) abortion is due to some form of human tragedy. Ironically, she also said government has no business being involved in healthcare. It's too bad that that does not track with all her other statements.

Have not grabbed this yet (56k'r) but wouldn't various forms of setdammage create the broken windows? Remember, there are two variants, crack and busted. I think just to put in to the readme to set the dammage in the init box would be the best solution.

Having picked up soldner solely to see how they tried to implement destructable buildings and extremely large land areas... the viewdistance (lod issues?) sucked compared to OFP, and the rough terrain does not lend itself to company+ armor manuvers. (What I want to see from OFP2: standardized LOD levels in a p3d dev.spec, so that everything balances; and keep the plains.) While the simplified buildings are nice, VBS apparently has that as well. (You hear that 3wx? That can be your moment to redefine OFP.) The destructable buildings are a farce without anything other than a c4 bomb. We've seen some intitial work done with replacing objects with pre-destroyed wrecks, that should be more satisfactory in the mean time. (What if... take the example of Hawk's Nimitz... place a generator script on the wrp, so that the ingame placement was dynamic? As buildings can be rigged in a fashion to allow for actions like doors, ladders, and waypoints, why not spawn a replacement when damage is x?) they did bother to put in -twomon support, but it is buggy when switching display modes. OFP is auto-correcting. (Thank you, and for -debug, and for -window, and for -x and -y, and all the others, and most importantly for telling us about them.) Beyond that... I was just thinking to myself wondering why OFP ever bothered with the civilian market in the first place anyway. It still is better than anything else out there, and even if the Spanels go get themselves fast cars and never show up for another day of work, the wreckage of OFP2 would have more potential than all the other pieces of hud out there. The fact that they are still busy coding away, and publicly have high hopes for porting to the confines of the xbox makes me really curious as to the dark majiks to come forth. So, how about some .plans?

Bad... and worse... Anyway, the whole reason for the power connecters on the topend cards is that the AGP slots on all the boards are pretty much at the limits. Problems especially showup on older nforce2 boards due to their underpowering. TomsHW had a rather nasty article on psu's a while back, basically said to knock 50 to 100+w off of the sticker rating, and don't push your luck. Have you tried updating your mobo bios?

What if... the object nucleous was a metalic lgm debris, but had accumulated a substantial amount of iced layering - methane, water, alien poo, who knows - and the iceball layers created the airburst, and the realtively small 'seed' survived? Takes care of both theories. Option two is that it is the leftover material from an alien attempt at 'Armageddon', basically them trying to shunt/shoot a comet headed their way, and we got it instead. In which case we need to go make contact to get their data to figure out if it worked or not. Option 3 is that somebody left their freezer door open somewhere so that it accumulated so much frost that it fell off of their flat earth and ended up here.

1. OFP 1.96 (rest in no particular order) 2. Total Anihilation 3. Quake2 4. Wolf3d 5. Tapper 6. Civilization / Freeciv 7. Nethack 8. Scorched Earth 9. Death Track A. Cmdr. Keen

Since we're on the subject of epochal chaos theory of 'minor' catastrophes, I'd just like to point out that in the current issue of IEEE Spectrum, that there is an excellent article detailing how the traditional statistical theoretical modeling for predicting the frequency and severity of significant power grid blackouts has been found to be significantly in error, with the probability of the larger end of blackout spectrum size being historically far outside of the traditionally held model. Given this example, along with the 'art' of predicting the probability of predicting other natural analog events (hello, the local fault lines look like somebody hit the windshield with a baseball bat), does science naively pad their numbers the wrong way, and can we legally hold them retroactively responsible for their whoopsie, since they are 'god' to the Insurance and liability industry? Since I can't sue God, I should at least be able to sue the scientists for screwing up their model, and causing me emotional distress when there is no actual threat, or liability for physical injury for failing to accurately warn of an actual threat. Now I'll be able to afford VBS1 and a nice sim-room after all.

For nvidia chipset AMD mobo's start here: nforcershq I have a Asus A7N8X-DLX Rev 2.0 and a A7N8X-E 2.0 both prior to the Ultra/400 northbridge fix. So I look under Asus topic and find this thread Current list of BIOS faults with the A7N8X-D Rev. 1 & 2 Try it with any other manufacturer for your mobo. Placebo: there was some rather esoteric analysis of similar crashes of SOF2 I think at the activision forums. The result was the same thing, too much heat. I got me a big huge case with tons of fans and that keeps everything between 40c to 50c all the time. I'm thinking of pluging a vent duct in the floor and hooking a flexy tube duct from the crawlspace under the house to the side of my box. I also made a pair of monitor coolers since I was cooking monitors as well. (Watch your ratings on them, they are rediculously low.) I use Motherboard Monitor to keep track of my temps, it's less laggy and intrusive than Asusprobe, and has lots more options as well. It also supports text logging.

Hmm... well that explains why I was having such a hard time trolling financial data on codemasters.

I had to knock my FSB back from 200 to 166 to get my machine to even boot. Do you have an nForce2 mobo? The AGP power on most of the boards is woefully underpowered, I found that out after putting in 2x512mb ddr400 and a 256mb gfx5600 that doesn't have a powerplug. The fix, if this is the case, is get a new mobo or significantly underclock your system. Check out nforcershq.com first though. They have the best databases on what models have the issues.

Has nobody else read the the old interview where UBI just about killed off OFP the first time? We wouldn't even be having this conversation if UBI had had the chance to completely skewer OFP up front. OFP is very unique. There is nothing else out there that comes close. OFP is a military-grade tactical simulator that just happens to be available commercially. You can't just compare it to anything else. Not to say that it is the best FS or navy-sim or FPS or best graphics, no, it's the genre. Codemasters had the sense to let BIS run with their ideas, and this is where it got them. My two bits: Ditch the xBox. pure console gamers will never willingly put up with the mindset of OFP, unless you gut the soul out of OFP. Cut your loses there, and use the experience gained to design tighter engine structures. If you do get stuck with Ubi from carry-over contracts, make sure that your open support of modding is garaunteed in the contract. Go dig through all the books about the corporate and social history of ID, and their publisher relationships. http://www.finance.ubi.com/en UBIP.PA Links to Ubi's annual reports and other stockholder information

Hmm... Why is patience so hard for 133t jedi? 1) VBS is handled by BIA/Colesceant, no 'significant' load there. People keep disappearing and reappearing with bless()'d email addresses... = business is growing... 2) Scant peeps about the xBox, except that being on the xBox and being OFP 1.5, it can't talk to the PC's... right now. conspiricy theory... maybe the net code is finally getting overhauled, and we will see major delaggage and JIP patches, as techdemo patches? 3) I strongly doubt everyone in BIA and Florida speaketh Czech. Maybe we could be seeing much improved tools too? 4) Remember that OFP is a totally different type of simulation, that's why the CS weanies don't like it, and the military does. All EA has to do is go to one vendor, license a sound engine, pick a LOD engine from somebody else, and blindly pick an AI/physics package off the shelf, feed it through the megabucks n00b packaging system, and presto, insta-game. That's not OFP, and I think BIS could be hiding the next generation of Uber-Architects in the Spanel brothers. 5) Go back and dig up the interview where Marek spills the beans about the whole life history of the Posiden project, and the companion history of dealing with publishers. The fact that we were even blessed with OFP at all... 6) Team Fortress 2. Total Anihilation 2. 7) The problem with rushing a product, is that if they had a quality product in mid early 05, would it run on win64, and would win64 be stable? Can we even do more than laugh ourselves silly at the notion of Microsoft shipping a reasonablely less-buggy OS? If BIS has all their wits together, and works their vendor connections with MS, etc., OFP2 could be the flagship Win64 sim/game, so good that it would be illegal for us civies to own or export it. In that case it's a good thing that Codemasters is a UK corp. 8) The problem with too many feature patches is that would take away the reason to buy ofp2, so we do kinda have to wait. 9) I'll be 26, and god-willing, I'll be around, but I can't predict between here and there any better than Codemasters can pull dates out of the air. 10) Since they are going to take their time and do it right, please post some additional manuals, at least for OFP2. To go along with the commented configs and comref, we also need official WRP specs and all the 'hidden' p3d names so we can make stuff too. Inshallah, all goes well, but a .plan would be nice. That's helped all the other games get and hold a high PR profile.

I'm curious to see what comes out in the SDK for D3 vs HL2. If you recall back to the design of Quake2, there was three main components: the exe (containing the graphics engine), gamex86.dll/.so for the actual game and physics, and the various 3d card driver wrappers. If Doom3 were to continue to follow this model, I think it would be quite reasonable to be able implement all sorts of things in a very cross-platform friendly environment, openGL instead of misdirectx.

On the original BIS Shilka, if the commander is sniped while turned out, the death animation slumps over, but then returns to locked upright position. Gunner and Driver stay slumped over. Also the AI driver can turn out, but there is no option for a player to turnout as shilka driver.

Click on the pics for 3200x1200. All shots using Kegety's dxdll. App-U is especiall nice to play with.

Do you have your view settings cranked way up and you are turning around a bunch? I noticed something like that when flying, I believe it was due to me flying faster than my PC could repopulate OFP's viewobject cache.