Wook

Revising my comment on Tree Bitmaps. I think the 'Low Res' bitmaps need to be revised. The 'High Res' Trees although adding tons more Polygons to the overall 'game environment' are less than well done compared to the 'Low Res' ones already in stock OFP. Basically if the 'Low Res' tree foliage was re-done to improve the look a bit, they'd more than make up for what was attempted by the high-polly 'High Res' trees. Trees however need an 'AI vision blockage' added to them in the upper foliage to stop the insane 'can't see you but can shoot you' behavior that the AI does unerringly. In stock OFP islands, more 'rocks' and random debris needs to pockmark the islands to give soldiers some place to run to cover. This includes more 'random junk' in some forests as they're made as if someone drives through with a bulldozer creating clear lanes everywhere throughout the whole island. Not that this needs to be 'over done' of course. Just, would like to see some extra boulders, rocks, brickpiles, woodpiles, trashbins [in towns], fallen trees, stumps, etc strewn throughout these prestinely kept islands. Martha Stewart's Everon is not the kind of island I'm used to visiting on manuevers. Wook [iDGN]

One that hasn't yet been mentioned is ... Russian - China Conflict. This is a very real possibility, as much as any other. There is plenty of historical conflict in evidence prior to modern times. One thing that NEEDS to be changed though... the Bitmaps for tReE's... must be upgraded. I find the 'Hi-Res' trees that add 'more branches' to actually look WORSE than OFP's 'Low-Res' tree bitmaps. It would be a great boon to see all tree types allowed in any one setting for an Island. So, that when you play Everon, you don't ONLY see the Everon style trees. However, I do not know if this is possible without so much conflict in the Mods to do so. BTW, FFUR 2007 2.0+ is incompatible with MP gameplay in CTI games. Both MFCTI and crCTI. Bummer. Would be GREAT if any future Mod focused on MP gameplay as its 'core' mission, instead of strictly SP gameplay for the loner gamer. Why do we even buy an MP game if all everyone's designing for is Solo gameplay? Anyways, have enjoyed the creative creations none-the-less. Wook [iDGN]

TB, would be grand if you could test this pack with MFCTI and crCTI before you close the book on this Mod. We're talking FFUR/FFSX the single best East vs. West Mod for OFP and still sllllightly incompatible with the best MP gameplay missions, MFCTI and crCTI. Random crashes early to midgame in MFCTI and crCTI. Wook [iDGN]

Tbird, fantastic. Uu-ragh! However, has this been tested with MFCTI? crCTI? Battlefield missions? That would be my hope. In MP groups at least. Wook [iDGN]

-Blazin sounds plannable. I'm currently not home and if I am home I'm in some hot water for being on this comp since this is July 4th vacation! Bugger it all! I just went out and ArmA'd yesterday too. On the verge of starting that up since my crew has more or less given up OFP since we just cannot agree on a mod that TC's OFP and lets us run it MP. WGL is good perhaps too good for what can be modeled in OFP gameengine-wise for realism. FFUR and FFSX though bring the feel of a new game in that the troops and vehicles and in general all the gear seems modern while WGL holds to some low-poly models instead. Eye-candy. Can't live without it to some degree when the peeps have 4+Ghtz machines to prance abouts on. We gave Y2k3 a run now 2 weeks ago but it's lack of recoil on weaps entirely makes it feel too teenage. But, Y2k3 does have a quite handy CD Player for music ingame which has given us a few laughs with it's customization. I'm in on some testing with FFUR or FFSX. Give me a week, since I'm currently not home. Really. Wook [iDGN]

Acidic, yes, its possible to change the models to HYK's. This will first and foremost have to be done through the Config.bin file located in the /bin/ directory. However, the FFUR and FFSX Addon probably has effects scripts tied to its use with its present model structure. To get the best usage the FFUR & FFSX Team would need to make the changes. Otherwise, you'll need to recode it yourself and try to track down whatever scripts are tied to the current models. Wook [iDGN]

Halochief, this is only doable by modding the config.bin file in the /bin/ directory. Since this base animation issue you have is with the altered movement styles modded by FFUR and FFSX. I'm unsure if this altered movement was required by FFSX animations or if it was simply a 'stylistic choice' by the FFSX team. Either way, the config.bin will have to be re-modded to fix your issue that was also pointed out earlier by Blazin as it affects and breaks several Stock OFP missions and Coops. Wook [iDGN]

Bug notices: Posting what we've noticed to try to help my crew determine if this is our side, a'la Addons we've got or if this is strictly FFUR 2007/FFSX in some cases. 1. MG on MG Tripod in some stock OFP missions.This breaks some missions. 2. KA-50 needs and REQUIRES both a Pilot and a Gunner or AI refuse to use weapon systems since apparently all Coops and stock OFP assume the KA-50 only has one trooper in it, the Pilot sans the Gunner. This breaks some Stock OFP missions. 3. Mi-17 East side officer cannot Pilot nor Gunner said vehicle if Player is Officer. Unknown if AI controlled officer can or cannot do so. AI Pilots and Gunners can be told to load, Pilot and Gunner positions normally. However, after AI Pilot and Gunner combo, they do not fire their weapons upon enemy troop forces. This breaks some Stock OFP missions. 4. Smoke affects only players in many cases where AI continue to shoot through smoke from explosions and burning vehicles with accuracy. Players however do not have this 'invisible smoke' capability. 5. Stock OFP Coop mission and some Campaign mission loadouts not realistic in primarily the case of West Sniper. 6. West Sniper has LOD issue showing white block's of untextured model at 55 meters and beyond. Unknown if affects latest version of FFSX, primarily noticed in FFUR 2007. 7. Ejection seats from KA-50 seems to be part of a problem of AI Targeting enemies. Further, damaged 'parts' from KA-50 seem to be part of an issue of AI Targeting 'unknown enemy' also. (Would further that this 'parts' issue also persists with other damaged vehicles. If a certain Class of 'damaged parts' are being applied to Air units in explosions then this may be a Global issue with Air Units. Unknown if this in fact is true, as to why this is being listed here for review.) 8. A-10 and KA-50 Ejection seats do not seem to disappear. Could be wrong about this point. Not completely convinced they do not, but, they are quite hard to track down in all cases. Would assume same situation with Su-25 ejection seat as well. 9. Blood spots from some troops do not seem to disappear ingame. Cannot define which troops this condition affects yet. Possibly some vehicle troops. Just quite unsure which troops are causing this condition. 10. M113 based vehicles have a very loud 'Clutch' sound. Do not remember off-hand if this persists in FFSX, I haven't been playing that lately as I enjoy the 'control' over my own trooper that FFSX takes away under fire. 11. Shilka's 'far' LOD is a flat green texture that appears to look as if the model is unfinished. Needs at least a placed 'black line' to indicate where forward gun's are facing to appear 'finished'. ~~Looked over this again and it needs a bit more than that. Lower turret break-line (split between Hull and Turret Ring) needs a 'line' or shadow due to how this nearly flat texture that almost appears to be more a placeholder than the finished texture appears. Hull texture needs a dab of shading either aft by the exhaust or forward by the driver's front hatch area to help indicate some idea of vehicle facing. Realism issues: 1. West ACOG Sight is under-zoomed. Presently ACOG zoom seems to basically equal the zoom of it's normal 'Iron Sights'. However, zoom mode for ACOG is 3.5x, for the original ACOG, to 5.5x in latest models. Present US Military issue is the ACOG TA01 4x32 from Trijicon I do believe. 2. Grenade toss seems just a bit shorter than I've seen most servicemen able to toss. Would extend about 25% more than presently modeled.

Blazin, I find it difficult to fathom how your whole squad is able to run FFUR or FFSX without crashing out your LANs. Thats my group's experience. Unless there is some re-mod you've done to stabilize the gameplay, I just don't see how at this time. We've got 5-8 guys who would run it if it would stop crashing out the server. We've cleared up alot of our particular issues. For example: The soldier's inability to climb stairs, ladders, etc. is due to an addon conflict with either USMC, BAS or Combat! soldiers. We're not quite sure which group. It could possibly just simply be any other soldier addon that this condition shows up in. So, FFUR and FFSX cannot do Coops that have any custom content beyond what stock OFP:Res provides I would have to suggest. In several stock OFP mission Coops the East 'MG' is often the PK model which is too low as it comes out on a MG tripod [appropriate of course] however, stock OFP sets up all East and West emplaced MG's on MG Posts for blockhouses, sandbag and roadblock emplacements. So, this breaks many many stock OFP missions. Disregarding these points, we still have guys crashing out midgame in many long and short run Coops. Reasons unknown. We've gone and assayed each person['s] directories to determine if they're inadvertedly running addons other than FFUR or FFSX. We've tried out the FFUR 2007 this week and seen the same issues. Previously we had only been using FFUR 2006 and FFSX 2007 as our base Addon. I would seriously like to see FFUR or FFSX running on a Public Server so we can really wring it out and fix these MP game crashing issues. ~~ Edit: Was just having a chat with one of the LAN crew and it was suggested that it could be possible that one cause for some crashing might be due to picking up ammo that contains more ammo in it than FFUR and FFSX allows. He noticed a time picking up the M24 SWS that showed up 16 rounds of ammo from a dead trooper when FFUR/FFSX only allow 5 rounds as he he was crashing out. Is it possible some missions have this sort of error that continually go unnoticed? I can think of several weapons where this type of bug [if it exists at all] could show up, M24SWS replaces M21 which normally has 20 rounds instead of the 5 alotted to a M24SWS of course. The Bizon with 64 is replaced by the VSS with 20. Just some thoughts. I would rather play FFUR or FFSX than OFP:Res anyday. Much more immersive and enjoyable.~~ Wook [iDGN]

Blazin, is your Squad using a Custom Modification of FFUR or FFSX? We had a good gaming weekend and my crew discovered: 1. Bloodspots that persist for hours after the troop they came from had died. 2. 'Enemy Objects' that our AI's attack but we have no clue what 'Objects' they are as they do not come up under 'targeting' that we can figure out. As per what I was able to find for TooTall with his Y2K3 mod in the past 2 weeks, I'm wondering if the "timeToLive" constant is not being applied to all objects that are not being subsequently called by a "deletevehicle" directive. Wook [iDGN]

Blazin, I've not seen a FFUR 2007. Good to know there is one somewhere. HYK Inf to replace the FFUR's customs that are unable to use ladders, stairs, etc? Wook [iDGN]

Blazin, did your whole clan actually run FFSX on that host? Also, Blazin, an addition to the 'Bugs List' is: Soldier LOD's blocking ability to use any ladders, stairs or simple inclines on boulders, rocks, and some buidling ledges. This limits the soldier's ability to find cover in combat environs which he is so placed. And, really limits just what you can do in OFP overall. Some missions require you to enter 2nd story buildings to 'rescue' or 'remove' certain key figures. So, this is a mission breaking feature for many OFP basic missions offered by the community and I do beleive 'breaks' a mission near the end of Resistance where instead you have to hand grenade the General in his 2nd story house. I actually cannot remember if he's on the 2nd story but remember the situation where I had to find a hand grenade on a dead OPFOR trooper to deal with the situation. Wook [iDGN]

I've not actually tried to run both at the same time. But, I'm almost sure that FDF is also a TC Mod [Total Conversion Mod]. If it is supplied with its own /bin/ directory, then no they cannot be run together. OFP can only execute one /bin/ directory from mods without seeing some very very very curious side effects. // Edit: There exists no Mod called "FFUR 07" nor "FFUR 2007". The progression of FFUR as it exists discountinued with "FFUR 2006". The successor to "FFUR 2006" is "FFUR+SLX" which has now been "accepted" in nomenclature as "FFSX". This Forum Thread is in regards to "FFUR/SLX 2007" as per the Thread Title however that title should be renamed to "FFSX 2007" if anything. Since FFSX is the simplest way to refer to "FFUR/SLX" aka. "FFUR+SLX". The issue that is confusing you is in the myriad of names that have been used to refer to this thread's specific 'new mod' branding. Hence forth, "FFUR/SLX" aka. "FFUR+SLX" is NOW REFERRED TO AS "FFSX" 2007. Hope that simplyfies all that naming mess for you. Edit end.// Wook [iDGN]

Because, with ArmA you can actually play it in MP without it crashing. Wook [iDGN] OK, thanks Wook, that explain why I'm been kicked off servers lately. I was not aware of this so I guess I'll play with Res then Escort, make NO MISTAKE, this is one exceptional Singleplayer Mod. I just very very humbly wish it was intended for Multiplayer. Absolutely. **Edit: One very curious thing about FFSX is that when it 'crashes' you out of the server, it takes the SERVER HOST down with it. Almost without fail, I'd further that about 80% of the time this is true. However, its predecessor FFUR 2006 when it crashes usually just takes you out alone. This is not exclusive as I have now seen on my own server instances where one person can be running FFUR 2006 and when they crash out its takes a couple people with them, entirely random. But, so far I'm not seeing FFUR 2006 actually crash our server host whether or not the server host is running FFUR 2006. But, if its running FFSX, then the host yet again dies when you crash too.** Wook [iDGN]

Ahhh, one small mistake on my part. With FFUR 2006 it crashes the clients out without crashing the server. With FFUR +SLX [now referred to as FFSX] it crashes out the entire server host. This is pretty bad in MP gameplay where the server has to be remotely rebooted after such FFSX crashes. Wook [iDGN]

Because, with ArmA you can actually play it in MP without it crashing. FFSX cannot be played in MP even if the server is hosting the mod. It still crashes randomly and for my group on LAN, pretty much every mission at some point. When one person crashes they often take with them 2 or 3, but, not all of us. Its strange and very random. All upgrades are done in order on all machines. We even tried Ghosting some directories to see if that was an issue. No joy. Wook [iDGN]

IS THERE ANY POSSIBLE WAY TO MAKE THIS WORK IN MP!?! We're running our own server hosting FFUR+SLX (FFSX I guess is the new name for it now?) and its still crashing the server out. Why is this happening? Seems to happen in any mission just about randomly. Coops, CTI's, anything. Yet, we can all play these same missions solo. Wook [iDGN]

Things I do not enjoy nor find realistic about FFUR+SLX (as opposed to strictly just plain FFUR without SLX). 1. Loss of my trooper's control over his actions. The automatic control of my trooper for PANIC situations should not occur. If I panic ingame, then my control over my trooper will reflect this on its own, I don't need the computer to TELL ME that I've paniced by taking control over specifically my trooper and then denying me the opportunity to play out my own response to the situation artificial by the CPU. 2. Use of the Artillery. When I play Battlefield, Assualt or any large-scale unit engagements, including CTI's, the Artillery fire that can be called in destroys entirely the opposing forces. While artillery is 'realistic' in warfare, the implementation in FFUR+SLX is less than realistic since there are no on-the-ground troops that can be surpressed, counter-batteried, setup, relocated, etc. to model this realisticly in OFP through FFUR. In Battlefield and CTI's that haven't crashed under FFUR+SLX up to that point of calling in Arty's it entirely wipes out the opfor yet again re-balancing OFP to strictly a F.O. Arty game instead of an Infantry/Armor Simulator. 3. Loss of control of my platoon/squad. While this does have realistic overtones its implementation is in need of fine-tuning. 1 MG bullet hitting next to a trooper running across an open field is NOT going to make that individual stop, drop and prone to be a stationary target in-real-life, IRL. If anything the "control loss" I'll have over that individual is going to be due to him/her rucking out to proper cover to save his/her life instead of just becoming Fire Drill MG fodder in the middle of that open field. These are really my only major issues with FFUR+SLX. I would PREFER that it would be MP compatible however. Sadly, that doesn't still seem to be the target audience of FFUR+SLX even though most everyone who has posted on this forum thread agrees that they enjoy MP gameplay, with friends or otherwise. FFUR+SLX to me still remains about the best East/West TC/Mod for OFP that is out there. And, as we all can plainly see, would be just completely awesome for MP gameplay. Wook [iDGN]

I've got quite a few Win98 / Windows 98 machines of 2Mhz and UP, 512MB RAM - 2GB Ram, 2T HDD's, etc. Will ArmA or ~CAN~ ArmA in any possible way be 'forced' to run on these machines? Oddly I have only one machine running WinNT and another running WinXP. Wook [iDGN]

I hope this thread has helped some folks a bit. I still haven't upgraded myself yet. So, ArmA is outta reach for a while for me. Wook [iDGN] ---Edit on my above last posting--- I meant there are some older CAD drivers that can let you use the memory 'hole' above the 1GB area not above the 2GB area. I'm unaware of any Win98 systems drivers that work with greater than 2GB RAM. So, note that slight change to my wording thereabove.

---Response to Blazin Edit--- Blazin, I would suggest you keep your 'Bug-List' posting near the last page, say, every 2-3 pages of new postings take, say this page 30th's 'Bug-List' posting and zero it out, pasting all its contents and any NEW content on say page 33rd's page. This would I think help Tbird and his code-team see that your list is as up-to-date as all the stuff from the pages that have been added since your page 30th 'Bug-List' posting. As far as how it would help Bohemia I think zeroing out [deleting all text and perhaps placing a "Updated on Page 33"] the data would reduce unnecessary data blanks for their Database. Just would help by reducing the content load for a list that would be increasingly more difficult to find, and more difficult to determine if the author [you] was in fact properly maintaining and upgrading the list of bugs as he [you] had stated as per your intent. Hope this assist everyone a bit. Wook [iDGN] ---prior-Edit--- Double posting edited out. Database Error popped up on this forum when I posted it. Reposted it as it didn't show up in the Forum Thread proper when I tried to review what I had written. See below for proper re-post. Wook [iDGN]

Tbird, thanks for helping keep FFUR alive and growing! **cheers** Really wish the FFUR sans SLX was also being worked as well. Its still my favorite MP mod for our gang here. But, its in need of some more fine tuning though. Wook [iDGN]

While I as of yet cannot run ArmA [don't have a WinXP machine up yet], I cannot imagine NOT having the original OFP color coding system for teams as it was working quite well. I, in absence of actually playing ArmA as of yet, would agree it is a feature I would want at least to have the OPTION of using 'pre-Qued' and 'single-keyed' as it was in OFP originally. I see the mechanics of how it works now in ArmA and see that it is much more limiting than its original implementation in OFP. **goes back to playing FFUR OFP sans the SLX upgrade, since thats not MP compatible at all** Wook [iDGN]

Most peripherals available today, meaning the majority of them, still are shipped with Win98SE / Windows drivers. Thank you, Suma. Good to hear from you so eloquently. Keeps me from messing up a perfectly stable system registry, *.ini and *.cfg files in an useless attempt to hope ArmA would run on one of these workhorses. Sadly that limits me to only one or at best 2 systems that can run ArmA outta the approx 11. I guess the LAN mates wil just have to get their own systems. Which, isn't going to happen unfortunately. Can't afford any OS upgrades. As it is a good friend gifted me XP for myself. However, I've actually yet to install it since the Win98 system its supposed to be used for just hasn't yet let me knock out its EULA! Privateguba, you can upgrade to 1gb RAM pretty easily, the trick is to set the vcache with MSCONFIG before you actually boot the OS and before you do your RAM upgrade. If you want more than 2GB there are a few system drivers that used to be distributed with some of CAD drafting packages back in the old days. To be honest, offhand I dunno which Ive used fot that older 2GB system. Just used to run fine with 2GB and Autocad 9 or 11 if I remember right. Unfortunately I'm unsure which version I used to run on it since its been mothballed for a while. But, it is a Win98SE system. Wook [iDGN]

I've got quite a few Win98 / Windows 98 machines of 2Mhz and UP, 512MB RAM - 2GB Ram, 2T HDD's, etc. Will ArmA or ~CAN~ ArmA in any possible way be 'forced' to run on these machines? Oddly I have only one machine running WinNT and another running WinXP. Wook [iDGN]