Adamski

Ah - I see the "slots" - thanks - I wondered why there was so much apparent duplication! Of course, you're quite right about the "28" - I was going to leave it "burned in" anyway. It just got me thinking about the numbering methodology as an aside, as I came to build the skin. Now back to the paint shop ;-)

Is there a way of getting at (and editing) the co-ordinates of where the aircraft numbers are placed on a model/texture? I'm doing a skin for ZK-WLM (based at Ardmore, New Zealand) and would like to place the number(s) on the nose, as opposed to on the rear fuselage. At the moment, I'm burning the number into the base texture, but would like to know if it's possible to use dynamic numbers. Adam.

Ouch! As simple as that? LOL! I looked so hard as well ... honest!!! "Occupy Set 1" and "Occupy Seat 2". I kept looking for front/rear/cockpit/instructor ... you name it! Many thanks :-) Adam.

I may be asking the same question. Is there a way of creating a single player/offline mission that allows you to jump back and forth between front and rear seat? Are there keyboard commands that do the switch (I couldn't find any)? What I'm after is the ability to fly from the front, but somehow enable the IFR hood so I can practise IFR approaches. Adam.

Yay!!! Thanks for the info. :)

I appear to have got this problem after the 1.52 update. It worked fine before. Nothing I can do will persuade my chute to deploy. When hitting the "P" key, I can see the cockpit animation/button moving but nothing happens. My hydraulics are fine (plenty of air) and all other systems are OK. I'm repaired/re-armed/re-fuelled etc. Still no go. Adam. EDIT: I double-checked: it *is* an air bleed - as shown in the gauge RH61. I have my wheel brakes set to an axis (foot pedals) as I thought it gave me better braking control. I'll try un-binding them and just using the W key. UPDATE: With the axis un-mapped, there' no air leak. I reverted to binding my left/right toe brakes to "W" with the Saitek control panel.

Brixmis - you're a star!! I was trying to do it from within the mission. Going to the main config screen and trying there did the trick! Many thanks!!!!

I had my Saitek Pro Pedals working fine in previous incarnations of DCS World (beta), but since the latest upgrade, I can't get them seen/recognised in DCS. They work fine for every other sim - and are seen by Win7x64 fine. Is there a config file somewhere where I could (manually) add them? Adam.

Worked for me! Many thanks.

I have the same problem, folks. Tried all the usual voodoo. Adam.

Well ...I get mixed results. 9 times out of 10 I either get a black screen or an inoperative players listing - where I can't click on a slot. Every once in a while, I actually manage to connect - with no problems at all. I can't work what makes one attempt work while others fail. The problem is that there's no escape from the dreaded black screen. ALT-F4 or Task Manager quit is all I can do. Not very elegant!!! Adam.

I'm really looking forward to this skin! Amazing, the level of detail that's going into it! Adam.

Aaah right ... thanks. I think I must be thinking back to old Falcon3 campaigns, where you'd fail the mission if you didn't spend enough time visiting the various CAP waypoints.

Thanks for the reply. Before I wreck my DCS install by playing with .lua files (LOL) ... Do you see the waypoints when in the mission proper (ie. F10 from in-aircraft)? I don't. I see them fine when creating/editing a mission, but can't see them anywhere else. OK ... so how would you cope with mission2 in the campaign (a CAP mission) if you've no idea where the CAP is meant to be? Without *editing* the mission, that is. EDIT: I swapped the two lua files over. I now get a kneeboard map (YAY!) - thanks - though it's quite zoomed in and doesn't show all the waypoints. However - still no route/waypoint layer showing in the F10 map. EDIT2: After a bit of fancy stitching from both LUAs, I managed to sort out the zoom problem (slightly). The real fix should ideally come from Leatherneck. The F10 map view problem remains though.

OpenBeta 1.50.45655 I'm starting the default campaign - but there are no waypoints or targets shown, either in the map view, mission briefing (or kneeboard). Basically, this makes the campaign *totally unusable* as you can't see CAP waypoints or mission targets (anywhere). How is one meant to proceed?

Thanks for that. I thought my sound setup was missing a few channels :lol:. At least my brakes still work!

Looking at some early videos, I noticed a pleasant hissing sound whenever brakes were engaged. Regardless of the state of my Co2, I don't get this sound (OpenBeta 1.5 and latest build of the Mig-21). I'm wondering whether these two things are related in some way <?>.

Hmmmm ... I'm on OpenBeta 1.5 and the latest MiG-21 build - and don't get to see waypoints shown on the map - ever. Also, the kneeboard function doesn't bring up the map (as shown in the manual). I had to go into the mission EDITOR to see where the hell I was meant to go!!!

John - let me add my vote of thanks for these highly polished videos. I've only had the MiG-21 a few days and these videos helped enormously, as the ED manual can be a little "cryptic" sometimes!!

Same here. I don't think it's O/S dependent (mine is Win7x64). It makes the campaign nigh-on impossible as mission #2 expects you to do some sort of CAP. Unless you go into the mission editor (cheating!!!) there's now way of knowing where your CAP waypoints actually are are.

Thanks George! I worked out half of it - but didn't know the "holding the mousewheel" trick! Is there a way of applying something similar for *external* views? When composing a screenshot., I sometimes want to pan a little left or right. Adam.

Can the viewpoint in any DCS aircraft be *panned* (sideways left/right, and up/down) without TrackIR? I can't seem to find a way of doing it. I get the all the usual angles (plus in/out) but can't raise/lower my viewpoint - or pan sideways. Help! Adam. Sure sign of madness - answering my own posts ... but I found it: RSHFT + RCTRL + NUM Keys does the trick!!!!

OK - I give up!!! I re-installed BS1. When run in standalone mode, it didn't ask for activation - presumably because my registry still has that info somewhere <?>. When running from DCS world, it won't accept the info that comes up. HELP! Adam.

Arrrrgh! That's what I was hoping to avoid - as I have no more space on that HD, since I removed BS1 to make room for DCS World, LOL! I've since added another HD and will reinstall BS1 and BS2 on that. Let's hope the DCS World doesn't mind some modules being on one drive and some on another. Thanks! Adam(ski).

Hello folks - it's been a LONG time since I've visited this forum! First-time install of DCS World went smoothly. My non-steam A-10C went in OK and I appear to have a flyable Su-35 and Mustang. All good so far ... ... however ... my Ka-50 (BS2) refuses to install into DCS world. I keep getting an invalid key error. I bought the original BS1 then upgraded to BS2 (both non-Steam). The FAQ says I have to re-run the installer. But *which* installer? I removed the old/redundant BS1 folder, running BS2 quite happily from it's own/new folder. No "installer" there, that I can see. Please don't tell me that I need to re-installl both original and upgrade from scratch - I don't think I have room on my HD! Is there any other way I can generate a new activation key? TIA, Adamski.