|
|
Forgot to add this: OS: WinXP Pro and DirectX9.0b installed, FS2_Open (tried every build I could find) run with the following commandline; -spec -pcx32 -jpgtga -d3d_no_vsync -fps -allslev -FOV 0.39 variations on the above did not have any influence at all. Further proof that this is caused by 'stars' is that when you set your speed to zero, so does the movement of these blocks stop. And before it is asked, the mission had $num stars set to 0. |
|
|
These aren't starts, they are the debris vclips and are loaded with every mission. I am unable to reproduce this problem in D3D or OGL and most of the other screen shots in that thread don't have this problem either. Using any strange registry settings? Does this only happen in the subspace mission of in normal missions as well? If only subspace then can you please make available the mission and graphics that show this problem? |
|
|
Please upload one of those screenshots to mantis |
|
|
That's space debris - the bug appears to be that instead of being alpha blended as it used to be they blen replacing the background. Thats why they appear black - when they normally should blend over the background. |
|
|
Upload your D3D caps please |
|
2004-04-28 07:17
|
subspace4.jpg (20,979 bytes) |
|
|
gosh, is it that difficult to click a link? K, I've uploaded a screenie of the bug in action...although I wonder why you just didn't take a look in the thread and rip a pic from there...and if you want more screenies, just click the link in the inital report... edited on: 04-28-04 03:19 |
|
|
D3D caps, not screenshots. |
|
|
i.e. a long text file you can generate from your launcher edited on: 04-28-04 07:23 |
|
2004-04-28 12:15
|
|
|
|
ah....my bad, sorry, thought you meant screencapture in D3D mode, it's attached |
|
|
perhaps it wouldn't be a bad idea if we give the mission designers the option of turning those things off. it certainly would make sense for subspace missions and the atmospheric missions that are seen in TI |
|
|
is it possible to adjust the density of the debris? instead of a on/off setting a slider would perhaps open up more options. |
|
|
Turning them off wouldn't be a problem. Adding a slider that would act as a divider for the number of times it can process means interface work so that's a bit more difficult. Having it all in the mission wouldn't be bad though and you could just specify the number of debris vclips you want at max, just like stars. |
|
|
[quote]"Adding a slider that would act as a divider for the number of times it can process means interface work"[/quote]ehm, in the interface it would require user intervention, not mission writer intervention, me thinks he more means a slider in FRED, or just the option of a $DebrisParticles: with a range from 0 to 100% to be interpreted by the engine similar to $Num Stars: ? |
|
|
I meant FRED2, sorry for not being specific. FRED2 would need the interface work to handle a UI option for the setting. That's not hard, just more work. I've already got "$Num Debris:" which has MAX_DEBRIS (currently 200) as the top end and 0 would turn the vclips off. The variable name can be changed if you want. This can be put in right after 3.6. |
|
|
fixed this, but havn't commited yet |
|
|
* BUMP * Bobboau, got this in CVS yet? |
|
|
PLease resolve this if it's in CVS. |
|
|
this has been fixed, and is in CVS |
- Anonymous
