Panzertard

ED hasn't informed any of us (community) about any patches specificly for DCS:BS ahead of DCS:W. We just have to wait, DCS:W changes alot in the DCS engine, and alot of bugs have been ironed out.

Here's a Quick & dirty Parser-->CSV I modded for DCS:BS/FC2 a while back. Can be opened in excel / filtered / sorted etc. I hope I have included all the files needed. You still need to make a copy of \X86 --> \X86\stable I think. EDIT: Just tested, still working. D:\nnnnnnnn\Config\Input\Input_parser>Input_to_CSV_eng D:\nnnnnnnn\Config\Input\Input_parser>run.bat parser-csv.lua D:\nnnnnnnn\Config\Input\Input_parser>set LUA_CPATH=..\..\..\bin\x86\stable\lua-?.dll;..\..\..\bin\x86\stable\?.dll D:\nnnnnnnn\Config\Input\Input_parser>..\..\..\bin\x86\stable\lua.exe parser-csv.lua --------------------------------------------------- Config #:1 File: A-10C.csv A-10C_joystick_Saitek Pro Flight Rudder Pedals {F20F8B40-8379-11de-8006-444553540000} A-10C_joystick_Joystick - HOTAS Warthog A-10C_joystick_Throttle - HOTAS Warthog A-10C_joystick_Saitek X52 Pro Flight Control System A-10C_joystick_F16 MFD 1 A-10C_keyboard_Keyboard A-10C_keyboard_default A-10C_joystick_Saitek X52 Pro Flight Controller A-10C_joystick_F16 MFD 2 A-10C_joystick_default A-10C_joystick_Saitek X52 Pro Flight Controller {F20F8B40-8379-11de-8005-444553540000} A-10C_joystick_CH PRO PEDALS USB --------------------------------------------------- Config #:2 File: A-10C_easy.csv A-10C_easy_joystick_F16 MFD 1 A-10C_easy_joystick_CH PRO PEDALS USB A-10C_easy_keyboard_Keyboard A-10C_easy_joystick_Saitek X52 Pro Flight Controller {F20F8B40-8379-11de-8005-444553540000} A-10C_easy_joystick_F16 MFD 2 A-10C_easy_joystick_Saitek X52 Pro Flight Control System A-10C_easy_joystick_default A-10C_easy_joystick_Saitek X52 Pro Flight Controller A-10C_easy_joystick_Saitek Pro Flight Rudder Pedals {F20F8B40-8379-11de-8006-444553540000} A-10C_easy_keyboard_default A-10C_easy_joystick_Joystick - HOTAS Warthog A-10C_easy_joystick_Throttle - HOTAS Warthog --------------------------------------------------- Config #:3 File: Default.csv Input_parser-CSV.rar

\x86\stable doesn't exists anymore, the parser-to-txt is outdated. You can trick it by making a extra copy \x86 -> \x86\stable I think it should work again after that.

Happy belated, old Viking. :)

So using a different Setup-kit (aka version 1.0.0) may perhaps solve it? And then patch it to 1.0.2 after that. Hm, you need to get hold of all the v.1.0.0 setup-files then perhaps. Other things you can try: - create a C:\Temp and rund the setup from there - use an external disk / usb / dvd to run the setup from there ... just to exclude the possibility that Windows is complaining about the source-dir you run setup from.

It shouldn't be a problem using that LoMac version. FC2 requires the following: - That a LoMac is preinstalled when you start SETUP.EXE for FC2. It will look for the previous product. You wont need Lomac installed after that. You wont have to install over Lomac, FC2 is standalone after it has been installed. You may uninstall Lomac after installing FC2.

E-mail addresses on DCS site and forums should be the same for correct user recognition. Please make sure you have the same e-mail's and after this go to http://www.digitalcombatsimulator.co...os=135&lang=en and the push "Request access to a closed Beta forum" button

When the FTP is overloaded it will ask for username & password and fail. Try using other alternative download methods until everyone is over the initial panic-download. :)

Wags, you should have put up the OpenBeta-manual so the gents had something to read while they wait for the download ;)

Ah, happy birthday you old tosser :D

I'll give the tech-guru a PM, see if he can have a look at it.

Why suddenly does it feel like the forums & webby is running on a 9600 kbit modem? :D I foresee a server overload or two the next few hours hehe

I still havent recieved a permit to enter the messtent after I accidently threw a cigarett into one of the YPV cask and torched off the place a couple of weeks ago. ... sobering up :(

If the DCS series is to be compatible online, which is intended, then all DCS modules will have to share the same virtual-world, objects and behaviour. Which in turn will mean, yes ... you'll be seeing these changed to DCS:BS. ... unless someone changes the plans for the DCS series that is.

Bump, you all need to wait for the next version in that case. :)

You're wrong, they wouldn't dare touching my delikate skin. :D Besides, finding a workaround for a problem is not considered as bad practice. If it is a problem in the first place I mean ;) If not, then it is a perfectly legal procedure.

Welcome to the club - you and I are keeping the service-crew busy! Jolly good! :D

Perhaps you can post a screenshot to illustrate where the shimmer occurs.

Bucic, I'll give you my own procedure, perhaps you can avoid the 'bump' this way? (Sorry, I havent watched your vidoes or anything) Assuming you have all damper channels aneabled except. And no FD. 1. Before I commit attitude change, press and hold trimmer. 2. Perform attitude change. Keep trimmer pressed. 3. Wait until the chopper 'settles' in the new direction. Still Holding the trimmer. 4. Controls center & chopper settled - release trimmer within a 0.5 second of centering the controls. This way I counteract any yay / oscilations at the end of the manouver. All that energy needs to settle and I have to smooth out the transition so the AP can cope with the new attitude. PPS, if there's alot of manouvering, several changes one after another, I wont release the trimmer until I've established a path I can hold. This means, sometimes, I can end up with trimmer pressed for 2-3 minutes when avoiding missiles and such.

Vsync shimmering? Or cloud over mountain shimmering? From my recollection: - Vsync can be managed by either enabling it or disabling it. - Possibly tuning the MaxFPS parameter will reduce some of the stutter for you. .\Config\graphics.lua. See Frazers tweaking guide word-doc p.8 - There's a anti cloud-shimmer mod somewhere. Unable to find it right now. Other similar threads with shimmer: http://forums.eagle.ru/showthread.php?t=55781

TEST.CMD @ECHO OFF Set MYFILE=D:\F-source\myimage.bmp Set MYDEST=D:\F-dest Set FILETYPE=*.BMP for %%i in (%MYDEST%\%FILETYPE%) DO ( ECHO Processing: %%i Copy /Y "%MYFILE%" "%%i" ) Try "FOR /?" in a cmd-prompt for more fun.

So it's related. Well, for the next version of DCS we are testing these scenarios, we can see some improvements. But I cannot promise anything until we have the final product of course ;) But a crash should not be a result of any taxiing. Care to share your mission, I could try to test a few scenarios with it? Both a 'working version' with no sim-crash and the version that causes the sim-crash.

Well, it could be that the AI/sim is faced with a impossible situation - and you enter a situation where the sim crashes. So basicly, this crash doesn't happen in any other missions then?

The ground traffic is a bit of a mess right now. Faced with similar dilemmas when returning to base, I've often given the different flights other airbases to land at to avoid congestion.

Hm, no obvious known problems in your Dxdiag. It's going to be a bit of a guesswork, but we have many people good at making suggestions here. :) What 'tweaking' were you doing btw? Mods? Some mods may introduce problems you cannot get rid of again, if they overwrote some of the sim-files. Tweaking as in Graphics-driver tuning? Can you retrace your steps and undo them? Otherwsie you can always try the classic update drivers, or downgrade them to an older versions. Requires a bit of work of course. :)