speedbird5

Hi, I want to build a home cockpit with a large wrap around (200 degrees field of view) curved screen about 3 meters in diameter and 2 meters high. I want to project only the outside view onto that screen using three high def projectors. How can I get just the outside view without the cockpit? What are the shortcut keys or commands to give me just that view? Here is a link to what I am trying to do... Scroll down to where it says "ACC F/A-18 Hornet" This is using Prepared 3d for the visuals.... https://www.natvis.com.au/case-studies Thanks.

Yes, that is correct, no visible result in the game. No effect whatsoever. Unacceptable shimmering and jagged edges. In-game MSAA and AF are off. My Nvidia control panel settings are below.

Wags, There is no way that I know to "enable these only through your graphics cards settings manager". I have a 1080ti, with the latest 382.53 drivers and have tried to set both AA and MSAA through the Nvidia control panel but none of these take effect. (There was an earlier post which said to ALT+ENTER to ensure the Nvidia control panel settings take effect but that does not work either) If you have managed to do it, can you tell us how by posting screen shots? Thanks.

Thanks for this. Ran the snapshot, no errors. Installed a mod into 2.0.4 successfully.

When do you think a new version may be available?

I have already been in contact with the developer of OvGME about this problem and it looks like he is going to fix this error. I am not sure if JSGME will be updated to handle this error. If OvGME is updated I think I will switch to it and use it for both 1.5.5 and 2.0.4

DCS 1.5.5 or DCS 2.0.4 ? If DCS 2.0.4, then could you post how you got it to work to assist others. Thanks

Hi all, Getting this error when I try to run an initial snapshot. Any ideas? I have all Visual C++ runtimes up to date. Am on Windows 10 x64. DCS 2.0.4. I get exactly the same error on exactly the same file on both 32 and 64 bit .exe The size of the file (Nevada.surface5) is... Size: 3.37 GB (3,619,422,496 bytes) Size on Disk: 3.37 GB (3,619,426,304 bytes) As an aside, JSGME gives me a "Stream Read Error" for 2.0.4 as well.

Hi all, I successfully installed JSGME for 1.5.5 using the procedure on the first page. However, when I follow the same procedure for DCS 2.0, when I try to run the initial folder snapshot, I get a "Stream Read Error". For both versions of DCS, I have used separate JSGME folders with different names with different shortcuts. I have just updated to 2.0.4.59188.134. Any ideas?

Well, I don't experience that with the F-15 in DCS and it would seem the OP, and others, don't either. I guess we will just have to agree to disagree.

And that's the point, isn't it? No aircraft I have flown induces PIO's in that manner. In my experience ( and I have 16000+ hours in military types and jet airliners in the real world ), the behavior of the DCS F-15 is unrealistic in that it induces these PIO's on the landing roll out with no wind, under normal, symmetrical braking. BTW, I can make the aircraft track the centreline, but you have to use techniques which one does not normally use. I agree that it needs to go back to the drawing board, and to me it would seem to be a rudder responsiveness problem (i.e. the lag to which you refer) which needs to be addressed - more so than the nosewheel steering.

No, I will have to disagree. You might call it realism, but IMO it is quite unrealistic. If the F-15 handled like that, with increasingly divergent oscillations as you try to correct to centreline, it couldn't have been certified. The original poster asked the question.... "F-15C - How to apply brakes without going off the runway?" We really shouldn't have to be answering that question.

OK, so I disconnected my rudder pedals and did some tests: Conditions: 1. No wind or cloud or turbulence in mission. 2. Mirage 2000 and F15, both landing at Groom. 3. Used the W key for brakes which applies brakes perfectly symmetrically (this is an assumption on my part) on both wheels (Right Ctrl+Enter to verify brake application) Results: 1. Mirage, landing on centreline - nosewheel on at about 135 knots. Press W key and hold until full stop. Dead straight and does not veer from centreline. 2. F15, landing on centreline - nosewheel on at about 135 knots. Press W key and hold until full stop. Veer from centreline at about 100 knots and off the runway into the dirt. 3. If you watch the control inputs on roll out (Right Ctrl+Enter), when you press and hold the W key, both brakes are applied in a symmetrical fashion and there is no rudder input at all. 4. From these tests I can conclude there is something in the F15 which either applies asymmetrical braking or some other type of lateral input which causes the divergence. The Mirage does not exhibit this problem under identical conditions.

What are you using for rudder control? How is it calibrated? What does the curve look like? What are you using for brake control? How is it calibrated? What does the curve look like? Do you have individual/differential brakes set up or is the brake application the same for both wheels? Why is it that I can use precisely the same curves and calibration for the Mirage 2000-C and not have any problems, yet with exactly the same settings in the F-15C, I get directional control problems?

BSS_Sniper is correct. You should be able to apply brakes continuously and easily maintain directional control. That's how it is in the real world with real aircraft, both military and civilian. The F-15 DCS simulation is deficient in fidelity with respect to braking characteristics and should be addressed. It greatly detracts from what is otherwise a great simulation for a desktop program. Proof of my statement is because in the Mirage 2000-C, with precisely the same axis curves for brakes and rudder as with the F15, I can bring the Mirage to a stop commencing braking at 100 - 90 knots and keep it straight until a full stop. No weaving. No "pulsing of brakes". This is definitely not the case with the F-15C. Could the developer please address this issue as it has been brought up in many posts and threads.

Ensure that the CAS is on for yaw, pitch and roll. Also the ARI should compensate for this. Check the Belsimtek manual. In real world aircraft, the secondary effect of rudder is roll. The first thing one is taught in training is "Effects of Controls". When one applies rudder, the advancing wing moves at a faster rate than the receding wing thereby creating more lift on the advancing wing and hence a rolling moment. Hence the roll you are observing with yaw. As an aside. The secondary effect of roll is adverse aileron yaw. The downward deflected aileron causes more drag (because it is creating more lift) than the upward deflected aileron and causes a slight yaw in the opposite direction to the roll. Not all aircraft exhibit this. As far as the simulation is concerned, I am not sure how realistic this is. I haven't had a chance to try it myself.

Here are two tracks which illustrate the problem using DCS 1.5.2 The first track is with the Saitek Combat rudder pedals unplugged. On landing, I apply brakes using the W key only with no rudder inputs at all. There is no wind in this mission. As you can see with only the brakes applied and no rudder input the aircraft veers off to the left and off the runway with only the W key pressed. The nosewheel steering is not deflected either. If you bring up the control inputs display with RCtrl+Enter you can see there are no rudder or aileron inputs on the rollout and brakes are applied symmetrically. The second track is with the Saitek Combat rudder pedals plugged in. On landing, I apply brakes using the toe brakes and try to keep the aircraft straight with rudder. There is no wind in this mission. The nosewheel steering is not deflected either. As you can see directional control is very difficult. My current rudder axis setting is attached to the first post on this thread. I do not use the Saitek SST software. F-15 landing-No Saitek Rudders - W key only.trk F-15 landing-With Saitek Rudders.trk

pr1malr8ge, thanks for the apology.

Thank you DerekSpeare. I am glad to have been of some help to you and maybe some others in the DCS community.

Pr1malr8ge, I posted one link to this thread. I have not "plastered" links and nor have I "insisted" people check out this thread. It is a common practice to post links to other threads when trying to assist people as so many other people have done in these forums. So I reject your inference. Sinusoid, I will post some tracks when able.

DCS has great potential, I am only trying to improve it. The fact that DerekSpeare, in his thread, "F-15C - How to apply brakes without going off the runway?" raises the same issue indicates there is a problem. I merely pointed him to this thread as it would give him perhaps more information. How is this a "constant barrage"? Who is "Coffcorpse" and why should I automatically know of him and why should I PM him? I would expect the developers to monitor the threads and respond to valid criticisms. (P.S. For the record, I am a real world pilot with over 16,000 hours on military types and Jet airliners, so I do have significant experience to back my statements)

I have come to the conclusion that the simulation is deficient in it's modelling of rudder sensitivity and damping in the landing roll above 50 knots. It is quite unrealistic in that regard. No amount of tweaking of the axis curves can fix it. I think it needs changes to the flight model which are beyond the user's reach. See this topic..... http://forums.eagle.ru/showthread.php?t=151735

Strikeeagle, do you have Saitek Combat rudder pedals?

Hi Pineapple, Yes, I already use that technique and alluded to it in my original post. My point is that we should be able to use brakes at say, 100 knots as I can successfully do in P3D in the VRS Superbug. Anyway, hopefully ED might address the rudder issue. Happy Thanksgiving to you and yours. No, I am not a Brit, but an Aussie.

Pete, I believe this to be a bug. See this thread http://forums.eagle.ru/showthread.php?t=152881 and this thread http://forums.eagle.ru/showthread.php?t=152882