Members in Shoutbox
None.
Shoutbox Search
Shoutbox Commands
/w [name] > Whisper
/r > Reply to last whisper /me > Marks as action Shoutbox Information
Moderators may delete any and all shouts at will.
|
Global Shoutbox
Please log in to shout.
[2015-6-30. : 2:22 am] Generalpie -- I wanted to show what something looks like in SC but Dxtory wouldn't cap it[2015-6-30. : 2:21 am] poison_us -- Dem0nDem0n shouted: FRAPS I've found Dxtory to be better than FRAPS[2015-6-30. : 2:13 am] lil-Inferno -- jjf28jjf28 shouted: you can usually just rely on eyes; theres always gonna be some delay for trigger execution; if you don't notice it, it's low enough That's not true. The human eye can only see 3 fps.[2015-6-30. : 2:06 am] jjf28 -- you can usually just rely on eyes; theres always gonna be some delay for trigger execution; if you don't notice it, it's low enough [2015-6-30. : 12:53 am] Alzarath -- Got Battle.net working. I went through hell to get it and all I had to do was install Microsoft's fonts.[2015-6-30. : 12:40 am] sigsaucy -- it is really hard to tell if the trigger lag is going away when i cut out triggers, is there a fps program i can use so i dont just have to rely on my eyes?[2015-6-29. : 11:40 pm] lil-Inferno -- Excuse me sir but you're under arrest. Your memes are too dank.[2015-6-29. : 11:28 pm] Moose -- Oh, I think skipped Theatre of War. That was a terrible map, possibly of meme quality.[2015-6-29. : 11:24 pm] Dem0n -- I was gonna say we should play your map some time, but all these maps are lame[2015-6-29. : 10:47 pm] Moose -- Of course, you'll try no triggers first. If you get lag with no triggers, it's not a trigger problem.[2015-6-29. : 10:45 pm] Moose -- You could try stripping out all the triggers and putting them back in sections to help pin down the problem triggers.[2015-6-29. : 10:34 pm] sigsaucy -- ive used hyper triggers in maps with more complicated triggers then in this one, i think itll end up being something pretty obvious[2015-6-29. : 10:22 pm] Moose -- You could always take that way out if you don't mind the hypers running 2x or 3x slower (depends what multiple you use)[2015-6-29. : 10:22 pm] Moose -- IIRC, in Astrogears, Tux had to use a slower version of hypers with 84ms or 86ms or some multiple (I forget the exact numbers) which made the triggers run that many times slower (but still much faster than normal)[2015-6-29. : 9:06 pm] Moose -- Unless he was talking about order of triggers, which for some implementations, they should be last. Regardless, when you make them shouldn't depend on the implementation. Unless you're still using StarForge lel.[2015-6-29. : 8:23 pm] Moose -- The better question is why is anyone still using a trigger editor where you can't reorder triggers and it matters what order you create the triggers in?[2015-6-29. : 6:56 pm] Azrael -- It seems like all your trigger timing would be off, and you'd have unexpected system breakages, if you finished a map first and then added hyper triggers.[2015-6-29. : 6:54 pm] Azrael -- NudeRaiderNudeRaider shouted: Roy depending on the implementation you want them to be the last triggers you create Can you elaborate? I don't know what you mean [2015-6-29. : 6:23 pm] NudeRaider -- paynepayne shouted: HI EVERYONE paynepayne shouted: how nice of you that this is the first message you want to share after all that time![2015-6-29. : 6:22 pm] NudeRaider -- RoyRoy shouted: Also, I don't understand how hyper triggers aren't the first triggers you make for any map. depending on the implementation you want them to be the last triggers you create[2015-6-29. : 5:41 pm] Vrael -- if one condition is much harder to calculate, you should probably put easier conditions first to avoid having to do "hard" calculations like bring conditions[2015-6-29. : 5:41 pm] Vrael -- so what jjf said in a different way, if 2 conditions are equally "difficult to calculate" put the less likely to be true one first to skip the calculation of the second one in the majority case[2015-6-29. : 5:40 pm] Vrael -- "less likely to occur" and "harder to calculate" both have an impact on the lag caused by condition checking[2015-6-29. : 5:35 pm] jjf28 -- so for example, always check your switches and death counters before checking a bring; if you have two brings, check the one that's less likely to be positive first[2015-6-29. : 5:33 pm] sigsaucy -- what i meant by harder to fulfill was less likely to occur, not harder to actually calculate[2015-6-29. : 5:31 pm] jjf28 -- it's better to put trivially cheap-to-check conditions first; after that it's better to put harder to fufill ones first[2015-6-29. : 5:27 pm] sigsaucy -- does order of conditions have any effect on processing speed? like if you have 2 conditions is it better to put the harder to fuflill one first?[2015-6-29. : 5:26 pm] sigsaucy -- ive made sure that the hyper triggers are at the bottom of the text editor list[2015-6-29. : 5:26 pm] sigsaucy -- im editing someone elses map hence the adding hyper triggers not first, i took out all the waits and put in death counters but theres some massive slow down going on |