I've validated my DirectX - my system happily runs the DX10 API on the Radeon embedded chipset without error. I can run 3D renders using Direct3D on Studio Max without error at 1920x1080 and have lots of texture maps at 20x48 x 4096, or even 4096 x 4096 and not have a failure with layering or crashing. I also do 3D modelling with Poser, and it's texture maps are equally as large, no issue with DirectX rendering either.:P
If my poor little system can handle doing full 1080x1920 rendering using much more graphic memory than ST:O, why is the game causing such failures? Also, why is it just after Season 8 launched?:eek:
Methinks the programmers went and tried to do a DirectX end-run to get more detail in by doubling up on map layers, instead of defining each map as a separate layer, or some such, and this is causing the failures for those of us effected. This is not generally permitted under DirectX programming as each map needs to be it's own defined layer, but that can consume more memory than doing a multi-layer map on a single layer.
It's been years since I did DirectX programming, however lots of games run it without issues. Why is ST:O failing after Season 8? What did the programmers do to cause the error?:(
We were the Borg, you should have been Assimilated, your Biological and Technological Distinctiveness was not added to our own, instead ... you exposed us to kittens.
It's a picture, a picture on the reload/loading screen that's messing it up. It is every single 4th load. It doesn't matter what that load is (respawn, mapswitch, etc) once it reaches the 4th, it crashes.
But hey, after missing a month with the last bug, at least I can play now. Silver lining in that Gravity Well.
Crashed four times just doing the Tour.
What, exactly, does "Material Files Reloaded" mean?
I'm gonna go get breakfast started for us, since it looks like we're gonna be together (again) on this thread now for a while. How y'all want yer eggs?
Apparently this is caused by some kind of bad load screen graphic, because it occurs only during load screens, and is triggered by one of the newer load screen splashes. Whenever it attempts to load a given load screen splash, BOOM. Otherwise, everything is fine. I am attempting to determine which one it is.
it isn't too bad now, it still crashes... so to get the stuff i need to do my dyson rep, i just sit on the ground battlemap. sometimes it crashes when i transport elsewhere, or respawn, so i just dont die or use the transporters
i cant log on holodeck error ticket 14180797 error dv: unable to find patchxfer.log but tribble works fine.. what i want to ask is how can this be,since its same version on both servers? i play STO 2years now,and i love it! it is one of best games i have played. please fix it
That might be a good sign--since you're not having troubles on Tribble (sorry 'bout the pun), then it sounds like the issue is fixed--and will hopefully be fixed on the next patch to Holodeck.
And how am I going to get the "Choice" of marks back from PvE???? I'm not, but it is my fault I guess....seeing how, you know, it is NEVER Cryptics fault. What excuse do you have now????
This issue has NOTHING, ABSOLUTELY NOTHING TO DO WITH THE PLAYER AND WHAT SYSTEM THEY RUN. Trying to blame the player/machines instead of just taking the blame and coming up with a resolution just shows us how much you really care........PATHETIC!!!!
it isn't too bad now, it still crashes... so to get the stuff i need to do my dyson rep, i just sit on the ground battlemap. sometimes it crashes when i transport elsewhere, or respawn, so i just dont die or use the transporters
that seems to fit....all we have to do is have a player with no problem mirrior our moves and we can figure out which one. seems to have lots of words on it i cant read it because it crashes
1357707
Dread, fear, & hope today's patch corrects our issue. Honestly, I would rather crash occasionally instead of being locked outta the game altogether.
There's enough Star Trek fans worldwide. We need to get organized, combine our funds, & buy STO from the powers that be. Then & only then, will things be ran properly. I have faith this can be done.
Geek revolution!
1357707
Dread, fear, & hope today's patch corrects our issue. Honestly, I would rather crash occasionally instead of being locked outta the game altogether.
There's enough Star Trek fans worldwide. We need to get organized, combine our funds, & buy STO from the powers that be. Then & only then, will things be ran properly. I have faith this can be done.
Geek revolution!
Comments
I've validated my DirectX - my system happily runs the DX10 API on the Radeon embedded chipset without error. I can run 3D renders using Direct3D on Studio Max without error at 1920x1080 and have lots of texture maps at 20x48 x 4096, or even 4096 x 4096 and not have a failure with layering or crashing. I also do 3D modelling with Poser, and it's texture maps are equally as large, no issue with DirectX rendering either.:P
If my poor little system can handle doing full 1080x1920 rendering using much more graphic memory than ST:O, why is the game causing such failures? Also, why is it just after Season 8 launched?:eek:
Methinks the programmers went and tried to do a DirectX end-run to get more detail in by doubling up on map layers, instead of defining each map as a separate layer, or some such, and this is causing the failures for those of us effected. This is not generally permitted under DirectX programming as each map needs to be it's own defined layer, but that can consume more memory than doing a multi-layer map on a single layer.
It's been years since I did DirectX programming, however lots of games run it without issues. Why is ST:O failing after Season 8? What did the programmers do to cause the error?:(
Crashed four times just doing the Tour.
What, exactly, does "Material Files Reloaded" mean?
I'm gonna go get breakfast started for us, since it looks like we're gonna be together (again) on this thread now for a while. How y'all want yer eggs?
If you want contact me in game Ill send you an invite to the Nova Elite KDF fleet. Youll be welcomed there even with the Disconnects.
Fleet leader Nova Elite
Fleet Leader House of Nova elite
@ren_larreck
Unfertilised......
Fleet leader Nova Elite
Fleet Leader House of Nova elite
@ren_larreck
Took far to long with the old thread...
What card are you running?
That might be a good sign--since you're not having troubles on Tribble (sorry 'bout the pun), then it sounds like the issue is fixed--and will hopefully be fixed on the next patch to Holodeck.
Fatal Error: Direct3D driver returned error code (D3DERR_INVALIDCALL) while creating a texture.
Technical Details: D3DERR_INVALIDCALL while creating 2D texture size 4096 x 2048 (1 mips,RTEX_DXT1,usage 4,Mgd y,GS N) Intel(R) G965 Express Chipset Family
Ticket number: 13577077
This issue has NOTHING, ABSOLUTELY NOTHING TO DO WITH THE PLAYER AND WHAT SYSTEM THEY RUN. Trying to blame the player/machines instead of just taking the blame and coming up with a resolution just shows us how much you really care........PATHETIC!!!!
Dread, fear, & hope today's patch corrects our issue. Honestly, I would rather crash occasionally instead of being locked outta the game altogether.
There's enough Star Trek fans worldwide. We need to get organized, combine our funds, & buy STO from the powers that be. Then & only then, will things be ran properly. I have faith this can be done.
Geek revolution!
Looking to make some friends?
Add me on Enjin or Check out the Federation Special Operation Initative.
http://thegamersrepublic.enjin.com/profile/1635733
Same error message