Jump to content

can not start from ground

Ed Hunter

By Ed Hunter
in Bugs and Problems

 Share

Recommended Posts

Ed Hunter

Ed Hunter

Posted
Posted

Hi All

having a odd issue with finale release

If i try to start a mission from the ground ether on runway or ramp the screen as soon as the game gives me control shows water on part of the screen and black on the rest. ??

No problem if i start in the AIR, do sent matter if its a mission out of the missions folder (was testing the free flight start in air good ramp or runway bad ) or a quick start mission.

any body have any ideas graphic settings are low or medium and have had no issues with the last 2 betas

Thanks

Stu

[sIGPIC][/sIGPIC]

ZMEY-HS-

ZMEY-HS-

Posted
Posted

Might be due to low ammount of ram. Sometimes, I had the same black-blue problem with 2GB of dd3 PC-10600(@1333) during flight. Plus, after around 15-20 mins of flight i got fps drop to 10-13 and stutters. There were no video glitches after i bougt 4 GB of dd3-12800(@1600), less stuttering and no fps drop.

colo

colo

Posted
Posted

Ed Hunter do you mean "Synchronize HOTAS..." option ?

I have this unticked but the problem persists...

Intel Core i7 11700, 32 GB RAM, Nvidia RTX 4090, NVMe 3 TB, VR HP Reverb G2, Thrustmaster Warthog + pedals, Cougar MFDs, TrackIR, aInstruments

Duckling

Duckling

Posted
Posted (edited)

Just made a complete new install of Win7 (32bit) on my old rig, version 1 and patch .6

Been running XP and Beta 3 earlier.

Water as background but nothing else seen. Thats true for ramp starts and a few training missions etc. Starting in air shows panels "distorted" and details missing here and there. Stick handle shown opaque and some other odd graphics overlayed here and there. I know this isn't much for a problem description but gotta catch some sleep before tomorrow. Tried the option above to uncheck the Hotas sync but no joy. Back to troubleshooting tomorrow ;-)

Since it a complete reinstall and upgrade before checking functionallity, the cause is a bit hard to track with all new drivers etc. Could it be Direct X related ?

 

ps. running on 2 gig only. additional is inbound . ds

 

Cheers

Gus

Edited by Duckling

- - - -

Duckling

Duckling

Posted
Posted

Thanks Nate , "tweaks" made or installed

Nvidia driver updated to 266.58

Win7SP1 (32), 4gig RAM

Sim installed and patch .6 remains as is (no modification)

 

Must be something I overlooked :-/

Greatfull for any input

 

 

pics below from the training missions

 

Pic6.png Pic5.png

 

Extract from "dcs" file:

00018.539 ERROR DXRENDERER: DXDefTextureManager: can't find gausse.bmp

00018.977 ERROR DXRENDERER: DXDefTextureManager: can't find rl_target_sprite.bmp

00018.979 ERROR DXRENDERER: DXDefTextureManager: can't find noise_beam_0_256x1.bmp

<snip>

00033.022 WARNING NGMODEL: Model '/models//uaz-469.lods' has invalid bounding box.

00041.799 ERROR WRADIO: "NDB" beacon is on the water!

00043.965 WARNING WRADIO: Map objects for beacon site Ялта NOT FOUND! Ojbects created.

00044.067 WARNING WRADIO: Map objects for inactive beacon site Мыс Кыз-Аул NOT FOUND! Ojbects created.

00045.077 WARNING WRADIO: Map objects for inactive beacon site Мыс Сухумский NOT FOUND! Ojbects created.

00045.151 WARNING WRADIO: Map objects for beacon site Мыс Евпаторийский NOT FOUND! Ojbects created.

00045.231 ERROR WRADIO: "NDB" beacon is on the water!

00045.231 ERROR WRADIO: "NDB" beacon is on the water!

00045.243 WARNING WRADIO: Map objects for inactive beacon site Мыс Железный Рог FOUND. Beacon linked to this objects.

00045.341 WARNING WRADIO: Map objects for beacon site Мыс Херсонесский NOT FOUND! Ojbects created.

00045.498 WARNING WRADIO: Map objects for beacon site Потийский NOT FOUND! Ojbects created.

00045.667 WARNING WRADIO: Map objects for inactive beacon site Мыс Анапский NOT FOUND! Ojbects created.

00045.691 ERROR WRADIO: "NDB" beacon is on the water!

00045.995 WARNING WRADIO: Map objects for inactive beacon site Мыс Кодошский FOUND. Beacon linked to this objects.

<snip>

00050.442 WARNING NGMODEL: Model '/models//an-26b.lods' has invalid bounding box.

<snip>

00054.751 ERROR LIVERY_MANAGER: Can't open livery '0' for model 'uh-1h'. Reason: no such dir or archive.

00055.128 ERROR LIVERY_MANAGER: Can't open livery '0' for model 'uh-1h'. Reason: no such dir or archive.

00059.860 ERROR LIVERY_MANAGER: Can't open livery '81st fs spangdahlem afb (sp)_01' for model 'a-10c'. Reason: no such dir or archive.

00075.883 ERROR COCKPITBASE: Cockpit::avDevice::link_all: unable to find link variable 'TGPinterface' for device 'MAIN_PANEL'

00075.883 ERROR COCKPITBASE: Cockpit::avDevice::link_all: unable to find link variable 'padlock' for device 'MAIN_PANEL'

00075.883 ERROR COCKPITBASE: Cockpit::avDevice::link_all: unable to find link variable 'betty' for device 'AAR47'

00078.762 WARNING COCKPITBASE: Cockpit: MapObjectsBuffer . Specific element 23 not implemented, map may be incorrect

00078.762 WARNING COCKPITBASE: Cockpit: MapObjectsBuffer . Specific element 24 not implemented, map may be incorrect

00080.263 WARNING COCKPITBASE: Cockpit: MapObjectsBuffer . Specific element 23 not implemented, map may be incorrect

00080.263 WARNING COCKPITBASE: Cockpit: MapObjectsBuffer . Specific element 24 not implemented, map may be incorrect

00081.175 ERROR COCKPITBASE: Cockpit: Clickable - Wrong connector name EW-LGT-R1

<snip>

00103.944 ERROR EDTERRAINGRAPHICS3: Material: edgemat FxMaterial_Runway31 terrain/shaders31/Runway31.fx|FOG_ENABLE|LIGHT_TEXTURE airfield_asphalt_06.png airfield_asphalt_06_nm.png black.tga black.tga 0

00103.944 ERROR EDTERRAINGRAPHICS3: dont bind geometry edgelgeom 37231258

00104.093 ERROR EDTERRAINGRAPHICS3: Material: edgemat FxMaterial_Runway31 terrain/shaders31/Runway31.fx|FOG_ENABLE|LIGHT_TEXTURE airfield_asphalt_06.png airfield_asphalt_06_nm.png black.tga black.tga 0

00104.093 ERROR EDTERRAINGRAPHICS3: dont bind geometry edgelgeom 37230e10

00106.657 WARNING NGMODEL: Model '/models//trees_1_blk.edm' has invalid bounding box.

00106.660 WARNING NGMODEL: Model '/models//trees_3_blk.edm' has invalid bounding box.

00106.662 WARNING NGMODEL: Model '/models//trees_5_blk.edm' has invalid bounding box.

00106.664 WARNING NGMODEL: Model '/models//trees_6_blk.edm' has invalid bounding box.

00106.666 WARNING NGMODEL: Model '/models//trees_7_blk.edm' has invalid bounding box.

00107.114 WARNING NGMODEL: Model '/models//trees_8_blk.edm' has invalid bounding box.

00107.116 WARNING NGMODEL: Model '/models//trees_9_blk.edm' has invalid bounding box.

00108.221 WARNING NGMODEL: Model '/models//trees_2_blk.edm' has invalid bounding box.

00108.360 WARNING NGMODEL: Model '/models//trees_4_blk.edm' has invalid bounding box.

00111.043 ERROR DXRENDERER: DXDefTextureManager: can't find white.png

00111.044 ERROR DXRENDERER: DXDefTexture: failed to load white.png. Reason: D3DXERR_INVALIDDATA.

00113.417 ERROR GRAPHICSXP: ModelManager: can't find LAP-CABLES

<snip>

00121.698 ERROR DXRENDERER: DXDefTexture: failed to load gausse.bmp. Reason: D3DXERR_INVALIDDATA.

00121.710 ERROR DXRENDERER: DXDefTexture: failed to load rl_target_sprite.bmp. Reason: D3DXERR_INVALIDDATA.

00121.720 ERROR DXRENDERER: DXDefTexture: failed to load noise_beam_0_256x1.bmp. Reason: D3DXERR_INVALIDDATA.

00127.962 ERROR DXRENDERER: Create texture "_resampleToLumMap" (RENDER_TARGET - D3DFMT_R16F) failed!, D3DERR_INVALIDCALL

00128.594 INFO DXRENDERER: Creating Resource "Unicode" of type 5

00133.760 WARNING FLIGHT: HELIPAD + FARP-1 has no ATC communicator!

00133.760 WARNING FLIGHT: HELIPAD + FARP-2 has no ATC communicator!

<snip>

 

Cheers

Gus

DCS10C_1.0.0.6errs.zip

- - - -

Distiler

Distiler

Posted
Posted

NVIDIA GeForce 7950 GT

 

Might be because of it?

  • Like 1

AMD Ryzen 1400 // 16 GB DDR4 2933Mhz // Nvidia 1060 6GB // W10 64bit // Microsoft Sidewinder Precision 2

Burner

Burner

Posted
Posted

I think that some of these issues are related to the 32 bit 3GB switch. Mustang's advice is good advice but, he fails to add a condition to the amount of RAM being used up. i.e. value set to allow some free RAM for other programs. I too had the same issues with the system bogging down after a short time flying and would need to reboot to fix the problem.

 

Here is the correct code for the boot.ini as I understand it now from some FSX friends who have used the switch for years.

 

"multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 3GB Switch" /fastdetect /3GB /userva=2560"

Burner

 

 

Intel Core i7 9700 @ 5.1Ghz, Nvidia RTX 2080Ti, Win 10 Pro 64 Bit, HOTAS Hornet, Virpil CM2 Base, MFG Rudders , HP Reverb Pro

Nate--IRL--

Nate--IRL--

Posted
Posted
I think that some of these issues are related to the 32 bit 3GB switch. Mustang's advice is good advice but, he fails to add a condition to the amount of RAM being used up. i.e. value set to allow some free RAM for other programs. I too had the same issues with the system bogging down after a short time flying and would need to reboot to fix the problem.

 

Here is the correct code for the boot.ini as I understand it now from some FSX friends who have used the switch for years.

 

"multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 3GB Switch" /fastdetect /3GB /userva=2560"

 

That would only apply to XP. In Vista and Win7 it is done differently.

 

Nate

Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
Burner

Burner

Posted
Posted

That is correct. I would hope that Win XP would be inferred by my Sig.

Burner

 

 

Intel Core i7 9700 @ 5.1Ghz, Nvidia RTX 2080Ti, Win 10 Pro 64 Bit, HOTAS Hornet, Virpil CM2 Base, MFG Rudders , HP Reverb Pro

Duckling

Duckling

Posted
Posted (edited)
NVIDIA GeForce 7950 GT

Might be because of it?

 

Distiler, Nate, Burner many thanks

Right on spot, Distiler. It related to either the 7950GT , driver or Win7 (cant say what of these) The "bad" card worked well under XP so I guess its a Win7 driver issue (tried at least three different versions but the all gave allmost the same results as the posted pics displays)

 

I swapped to the even older X1650 and the graphics returned to normal. Application "crash" when quitting also gone :thumbup:

 

Since I made a complete new installation of win7 , and also rebuild the rig with "new" cards and drivers, also the new app and patch it's hard to track down the cause. Babysteps next time for me :smilewink:

 

I know these cards are oldies as my rig and both needs a refresh, but know I'm at least able to start it up.

 

Cheers

Gus

Edited by Duckling

- - - -

colo

colo

Posted
Posted

I have try Nate's signature tips (I have added /3GB switch, reinstalled DirectX and C runtimes) and instead of water and white screen now I have black screen plus movable mouse cursor as bonus :)

 

BTW with /3 GB switch Flamming Cliffs 2 planes don't have right textures...

 

 

[Win XP SP3 32 bit, DX9, 2G RAM, Radeon HD 5770 1GB, AMD Phenom X2, TrackIR 4]

Intel Core i7 11700, 32 GB RAM, Nvidia RTX 4090, NVMe 3 TB, VR HP Reverb G2, Thrustmaster Warthog + pedals, Cougar MFDs, TrackIR, aInstruments

colo

colo

Posted
Posted

white screen on ground solved -

I have try to upgrade to 4GB RAM but the problem persist,

but when I uncheck HDR option in graphics options everything looks good

Intel Core i7 11700, 32 GB RAM, Nvidia RTX 4090, NVMe 3 TB, VR HP Reverb G2, Thrustmaster Warthog + pedals, Cougar MFDs, TrackIR, aInstruments

 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...